You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using Pyrra to define SLI for services that have multiple deployments (e.g., DEV, QA, UAT, and PROD). My goal is to reuse the same SLI definitions across these environments but apply different target thresholds to facilitate testing and progressive rollout of rules.
A challenge I'm facing is that some of our non-production environments are intentionally shut down during off-hours (nights and weekends). This scheduled downtime skews the metrics and makes it difficult to get an accurate picture of service performance in those environments.
I'm wondering if Pyrra offers a mechanism to temporarily pause or ignore metric calculations during these known inactive periods. Ideally, this would function similarly to the active_time_intervals feature in Alertmanager, allowing us to define periods when metrics should not be considered for SLI calculations.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Pyrra community,
I'm currently using Pyrra to define SLI for services that have multiple deployments (e.g., DEV, QA, UAT, and PROD). My goal is to reuse the same SLI definitions across these environments but apply different target thresholds to facilitate testing and progressive rollout of rules.
A challenge I'm facing is that some of our non-production environments are intentionally shut down during off-hours (nights and weekends). This scheduled downtime skews the metrics and makes it difficult to get an accurate picture of service performance in those environments.
I'm wondering if Pyrra offers a mechanism to temporarily pause or ignore metric calculations during these known inactive periods. Ideally, this would function similarly to the active_time_intervals feature in Alertmanager, allowing us to define periods when metrics should not be considered for SLI calculations.
Thanks for your help
Beta Was this translation helpful? Give feedback.
All reactions