Incorrect mapping of NoData\Error to multidimensional rules

[yuri-tceretian]

What happened:

Execution of NoData\Error set to Ok or Alerting of multi-dimensional rules creates a new alert instance instead of setting the state of existing instances.

Example

firefox_ogGiPhA9F7.1.mp4

What you expected to happen

State of the current alert rule instances should be set according to the mapping options.

How to reproduce it (as minimally and precisely as possible):

• Create a rule that returns multi-dimensional results
• Wait util it is evaluated.
• Make data source provide either NoData or Error
• Wait for the next evaluation
• See that a new state is created.

Anything else we need to know?:

Environment:

• Grafana version: main-4a7ecc24
• Data source type & version: N/A
• OS Grafana is installed on: N/A
• User OS & Browser: N/A
• Grafana plugins: N/A
• Others: N/A

[jasuade]

Hey @yuri-tceretian, team, we have an escalation open regarding this topic. Thus, I wanted to ask if there is expected timeline to change this behavior or what would be the proposed action.

Thank you!

[yuri-tceretian]

We discussed this issue at the weekly meeting and decided to have a PoC of the fix to estimate the outcome and affected area. We're still evaluating the proposed solution.

[jasuade]

Thank you for the heads up @yuri-tceretian !

[jasuade]

Hello @yuri-tceretian, just wanted to catch up with the team on this issue. Was the PoC successful, were you able to estimate the outcome and impact, is there any timeline for the fix?

Thank you for all the work!

[yuri-tceretian]

Yes, I plan to finish the PR this week. There is another problem with state management I am addressing at this moment.

[Sheldun21]

Hey @yuri-tceretian I wanted to follow up as I saw this ticket reopen from our side.

Any luck with getting this completed/implemented?

Thanks for all you do!! :)

[yuri-tceretian]

@Sheldun21 I am working on this. It takes more time than I expected mostly because I found some significant problems in our tests.

[yuri-tceretian]

The PR has been merged. Please keep in mind that the change is behind a feature flag alertingNoDataErrorExecution and disabled by default. In the future minor, we enable it by default and then eventually remove the feature flag.