Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global Services should **not** reset metric counts #149

Open
6a6d74 opened this issue Jun 28, 2024 · 0 comments
Open

Global Services should **not** reset metric counts #149

6a6d74 opened this issue Jun 28, 2024 · 0 comments

Comments

@6a6d74
Copy link
Collaborator

6a6d74 commented Jun 28, 2024

Agreed at the Global Services test preparation meeting in Japan - the Guide needs to be amended to reflect this decision.

Global Monitors should implement alerts based on the change in a "count" metric value (i.e., where a metric is incremented following a given event). The absolute value of count metric will vary between Global Services - but the change over a common period should be similar.

Consequently, we would like Global Services to not reset their metric counts arbitrarily - because this would mess up the change comparison by the Global Monitor.

Obviously counts will get reset from time to time (e.g., when the service is restarted, or the the count gets high enough that the it resets itself) - but these events should be infrequent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant