coralogix_slo_v2 grouping unexpected new value

[ben-wilson-mews]

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.this["<redacted>"].coralogix_slo_v2.<redacted>, provider
│ "provider[\"registry.terraform.io/coralogix/coralogix\"].coralogix-prod" produced an unexpected new value: .grouping.labels: new element 1 has appeared.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

This happens when updating the SLO query to add a new grouping key. Doing this via the UI manually does not produce any errors.

[celaus]

Hi - this has been reported to the backend team. They are wondering if you can provide an example (or verify that our examples reproduce the error)?

[ben-wilson-mews]

Hi - this has been reported to the backend team. They are wondering if you can provide an example (or verify that our examples reproduce the error)?

Hey @celaus apologies I missed the response.

sum by (http_route) (
  aspnetcore_request_duration_cx_bucket {
    service_name = '${local.service_name}',
    le = '${local.latency_duration}.0',
    http_method != 'OPTIONS',
    http_route != '',
    http_route !~ '${join("|", local.low_request_count)}'
  }
)

-->

sum by (http_route, service_name) (
  aspnetcore_request_duration_cx_bucket {
    service_name = '${local.service_name}',
    le = '${local.latency_duration}.0',
    http_method != 'OPTIONS',
    http_route != '',
    http_route !~ '${join("|", local.low_request_count)}'
  }
)

The key part being changing the sum by () statement is what triggers this. Weirdly don't have it with click-ops, it's only via the terraform provider.

Anything with an aggregate like that should produce it, nothing special with that metric