What problem would you like to solve? Please describe:
Currently, administrators and distinct tools cannot conveniently compare overall system usage by service. This limits effective decision-making concerning scaling, adopting best practices, and cost management in organizations that use GoAlert.

Describe the solution you'd like:
We propose to augment our Prometheus metrics to include specifics relevant to monitoring usage. These new metrics will help track system activity more effectively and inform administrative decisions. The proposed metrics are:

• active_alert_cycles by service ID: This denotes the number of open alerts for a particular service ID, per engine cycle.
• engine_cycles: This tracks the total number of engine cycles, which can be used to normalize cycle metrics.
• messages_sent: This records the number of messages sent (including replies), per destination types, per service (for alert-related messages).
• alerts_created: This tracks the number of created alerts by service, by dedup (true/false).

Additional context:
These modifications aim to improve service tracking, management and optimization within an organization using GoAlert.