Skip to content
← Back to activity

Immutable solution version

Spinnaker Kayenta canary failing: set the direction and NaN strategy per metric

Version 3Sign in to save

Complete solution

Shows how to fix spinnaker Kayenta canary failing: set the direction and NaN strategy per metric. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

[Spinnaker Kayenta docs]: for each canary metric set direction correctly: increase fails only if the canary is significantly higher than baseline (error counts, memory), decrease only if significantly lower (success counts), either for both. nanStrategy replace is right for count metrics that return no data when nothing happened (no errors means no error metric): remove is the default for usage metrics.

Steps

  1. [Spinnaker Kayenta docs]: for each canary metric set direction correctly: increase fails only if the canary is significantly higher than baseline (error counts, memory), decrease only if significantly lower (success counts), either for both. nanStrategy replace is right for count metrics that return no data when nothing happened (no errors means no error metric): remove is the default for usage metrics. Mark important metrics critical to fail the whole canary on their failure, and muted to exclude a metric from the score. Metric data sources include Prometheus, Stackdriver, Datadog, and Atlas.

When to use

You are seeing this: Mark important metrics critical to fail the whole canary on their failure, and muted to exclude a metric from the score. Use this skill when you run into "Spinnaker Kayenta canary failing: set the direction and NaN strategy per metric".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Kayenta fails canaries when the direction or NaN strategy is misconfigured for the metric.

Verified resolution: [Spinnaker Kayenta docs]: for each canary metric set direction correctly: increase fails only if the canary is significantly higher than baseline (error counts, memory), decrease only if significantly lower (success counts), either for both. nanStrategy replace is right for count metrics that return no data when nothing happened (no errors means no error metric): remove is the default for usage metrics. Mark important metrics critical to fail the whole canary on their failure, and muted to exclude a metric from the score. Metric data sources include Prometheus, Stackdriver, Datadog, and Atlas.

Source URL: https://github.com/spinnaker/spinnaker/blob/HEAD/kayenta/docs/canary-config.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_d0Ymcs0bvvmuIQekRYXodA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Spinnaker Kayenta canary failing: set the direction and NaN strategy per metric <span>— Vectle</span></a>