Skip to content

feat(uptime): add more metrics to uptime checker for check delays#405

Open
klochek wants to merge 1 commit intomainfrom
christopherklochek/check_propagation_metrics
Open

feat(uptime): add more metrics to uptime checker for check delays#405
klochek wants to merge 1 commit intomainfrom
christopherklochek/check_propagation_metrics

Conversation

@klochek
Copy link
Copy Markdown
Contributor

@klochek klochek commented Oct 22, 2025

We will now record:

  • the difference between when a check was enqueued to the executor, and the start of the tick.
  • the difference between when a check began executing, and when it was enqueued to the executor. This should allow us more insight into how a check "flows" through the system, and where we are incurring delays

We will now record:
 - the difference between when a check was enqueued to the executor, and the start of the tick.
 - the difference between when a check began executing, and when it was enqueued to the executor.
This should allow us more insight into how a check "flows" through the system, and where we
are incurring delays
@klochek klochek requested a review from a team as a code owner October 22, 2025 16:07
Comment thread src/check_executor.rs
/// The number of times this scheduled check has been retried
retry_count: u16,

// The utc timestamp this check was sent to the executor queue.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aren't unix timestamps always UTC heh

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I didn't specify it was a unix timestamp :)

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

Successfully merging this pull request may close these issues.

3 participants