Skip to content

Conversation

@priteau
Copy link
Member

@priteau priteau commented Nov 23, 2025

The existing thresholds were:

  • expiry in more than 300 days: green
  • expiry between 140 and 300 days: yellow
  • expiry in less than 140 days: red

These large values mean that Let's Encrypt certificates are always displayed in red because they are currently valid for 90 days.

Adjust thresholds to be more useful:

  • expiry in more than 30 days: green
  • expiry between 7 and 30 days: yellow
  • expiry in less than 7 days: red

The existing thresholds were:

- expiry in more than 300 days: green
- expiry between 140 and 300 days: yellow
- expiry in less than 140 days: red

These large values mean that Let's Encrypt certificates are always
displayed in red because they are currently valid for 90 days.

Adjust thresholds to be more useful:

- expiry in more than 30 days: green
- expiry between 7 and 30 days: yellow
- expiry in less than 7 days: red
@priteau priteau self-assigned this Nov 23, 2025
@priteau priteau requested a review from a team as a code owner November 23, 2025 20:25
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the color thresholds for certificate expiry in the Grafana home dashboard. The new thresholds are more practical, especially for services using Let's Encrypt certificates, and the change correctly implements the logic described. I have one suggestion to improve the maintainability of the threshold values by using Jinja2 expressions to make them self-documenting.

@priteau priteau merged commit baf6b71 into stackhpc/2025.1 Nov 24, 2025
21 of 22 checks passed
@priteau priteau deleted the grafana-certificate-expiry branch November 24, 2025 13:20
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