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

feat(crons): Record tick decisions during clock ticks #80703

Conversation

evanpurkhiser
Copy link
Member

@evanpurkhiser evanpurkhiser commented Nov 13, 2024

This actually uses the system_incidents record_clock_tick_volume_metric to record decisions and transitions as metrics.

In the future we will use these decisions to dispatch unknowns as well as use them as part of the incidents outcomes consumer to determine if an outcome can be dispatched.

Part of GH-79328

This actually uses the system_incidents
`record_clock_tick_volume_metric` to record decisions and transitions as
metrics.

In the future we will use these decisions to dispatch unknowns as well
as use them as part of the incidents outcomes consumer to determine if
an outcome can be dispatched.
@evanpurkhiser evanpurkhiser requested a review from a team as a code owner November 13, 2024 22:07
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 13, 2024
@evanpurkhiser evanpurkhiser merged commit 3ae2f67 into master Nov 14, 2024
49 of 50 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/feat-crons-record-tick-decisions-during-clock-ticks branch November 14, 2024 15:11
@github-actions github-actions bot locked and limited conversation to collaborators Dec 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants