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
Datadog analyses that don't specify a version default to v1 and the new field aggregatordefaults to last in the CRD. So, an existing v1 analysis will fail with this error:
time="2024-06-17T10:24:26Z" level=warning msg="Measurement had error: Aggregator is not supported in v1. Please review the Analysis Template." analysisrun=podinfo-856d6c544-278-4 metric=latency-slo namespace=example
This test is not catching this case because the metric object doesn't reproduce the default last value of aggregator.
when migrating from Argo Rollouts 1.6.x to 1.7.0, the next run will fail with:
time="2024-06-17T10:24:26Z" level=warning msg="Measurement had error: Aggregator is not supported in v1. Please review the Analysis Template." analysisrun=podinfo-856d6c544-278-4 metric=latency-slo namespace=example
Expected behavior
The analysis should still use the implicit apiVersion v1 and thus pass.
Screenshots
Version
v1.7.0
Logs
time="2024-06-17T10:24:26Z" level=warning msg="Measurement had error: Aggregator is not supported in v1. Please review the Analysis Template." analysisrun=podinfo-856d6c544-278-4 metric=latency-slo namespace=example
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
aguiraorodriguez
changed the title
Broken DataDog v1 analyses by default in v1.7.0
Broken Datadog v1 analyses by default in v1.7.0
Jun 17, 2024
aguiraorodriguez
changed the title
Broken Datadog v1 analyses by default in v1.7.0
Broken Datadog apiVersion v1 analyses by default in v1.7.0
Jun 17, 2024
Checklist:
Describe the bug
Datadog analyses that don't specify a version default to
v1
and the new fieldaggregator
defaults tolast
in the CRD. So, an existing v1 analysis will fail with this error:This test is not catching this case because the metric object doesn't reproduce the default
last
value ofaggregator
.To Reproduce
Given this spec of an analysis:
when migrating from Argo Rollouts 1.6.x to 1.7.0, the next run will fail with:
Expected behavior
The analysis should still use the implicit apiVersion
v1
and thus pass.Screenshots
Version
v1.7.0
Logs
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: