# Update the SNS Root's canister\_status API

**URL:** <https://forum.dfinity.org/t/update-the-sns-roots-canister-status-api/28500>\
**Category:** Developers\
**Tags:** sns\
**Created:** [March 16, 2024, 12:10am UTC](https://forum.dfinity.org/t/update-the-sns-roots-canister-status-api/28500 "2024-03-16T00:10:41Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![icme](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/icme/32/4327_2.png) [@icme](https://forum.dfinity.org/u/icme)\
**Post date:** [March 25, 2024, 8:41am UTC](https://forum.dfinity.org/t/update-the-sns-roots-canister-status-api/28500/5 "2024-03-25T08:41:07Z")

</div>

Sure!

Pros:

- Makes additional metric information about SNS canisters available to SNS developers, or those who wish to help monitor SNS canisters (achieves parity with non-SNS canisters). Many SNS canisters have frozen in the past, so I’m building a solution that will help monitor SNS canisters and provide additional visibility for their DAOs.
- Being able to see the `memory_allocation` metric could have helped to prevent [this issue](https://forum.dfinity.org/t/openchat-proposal-to-temporarily-unregister-the-userindex-canister-from-the-sns/27087)
- Freezing threshold & idle cycles burn are important stats in order to determine at what amount of cycles the canister will freeze
- Cycle balance is already public via the current API, so there is no additional attack vector that isn’t already (potentially) exposed by the current API.
- Having more canister data metrics is generally good?

Cons:

- Development time is required (albeit very little dev time)
- You probably want to keep this up to date as the `canister_status` API evolves (i.e. adding query metrics)

---

_[View the full topic](https://forum.dfinity.org/t/update-the-sns-roots-canister-status-api/28500)._