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 - 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)