# Trouble Adding New Metrics **URL:** \ **Category:** Memfault Help\ **Created:** [May 31, 2022, 6:48pm UTC](https://community.memfault.com/t/trouble-adding-new-metrics/578 "2022-05-31T18:48:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jbahr](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@jbahr](https://community.memfault.com/u/jbahr)\ **Post date:** [May 31, 2022, 6:48pm UTC](https://community.memfault.com/t/trouble-adding-new-metrics/578/1 "2022-05-31T18:48:39Z")
I have an existing firmware application that already uses memfault metrics and successfully sends heartbeats on a timer. I added 2 metrics and while running the debug build on a single device I get the following error in the web UI when looking at the heartbeat: ![image](https://canada1.discourse-cdn.com/flex030/uploads/memfault/original/1X/0e9da4ea9cc65a6017acec675a18a42c54d799d9.png) The last 2 items in the list shown in the image seem to match what I expect for the 2 metrics I added. Also, I added the new metrics via Settings in the web UI, though I’m not completely sure I did that correctly. Do I have to load a new version of firmware to memfault that supports the new logs. Right now the device is reporting an existing firmware version even though it is a debug build with additional metrics. ---
**Author:** ![noahp](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.memfault.com/noahp/32/46_2.png) [@noahp](https://community.memfault.com/u/noahp)\ **Post date:** [June 1, 2022, 2:10pm UTC](https://community.memfault.com/t/trouble-adding-new-metrics/578/2 "2022-06-01T14:10:31Z")
Hi @jbahr , I’ve replied via [support@memfault.com](mailto:support@memfault.com) , thanks for posting the question! If anyone else ends up here- the answer is yes, the symbol file does need to be uploaded for Memfault to decode metric values. If the firmware changes, a matching symbol file needs to be uploaded.