Your metric query has been transformed into a query that is compatible with the previous infrastructure metric format -- what does this mean?

On my dashboard I see a little warning sign (triangle with exclamation mark, :warning:) next to the name of some graphs. The tooltip reads “your metric query has been transformed into a query that is compatible with the previous infrastructure metric format”.

What does this mean? Should I do something, like change the format of the metrics I ingest into New Relic, or the query for my graphs?

Hi there @dschridde -

Thank you for bringing this to the community. There could be a few reasons that this is happening. Could you please take a look at the known limitations listed here:

https://docs.newrelic.com/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql#known-limitations

If you do not believe that your queries are bumping up against any of these limitations, we can dig deeper with you!

Thank you!

Sadly cannot get the :warning: to go away even after reading those instructions.

Originally I had:

FROM Metric SELECT max(k8s.container.cpuUsedCores) AS 'Used', min(k8s.container.cpuRequestedCores) AS 'Requested', min(k8s.container.cpuLimitCores) AS 'Limit' WHERE k8s.namespaceName='...' AND k8s.containerName='...' AND tags.app='...' TIMESERIES

I read in the documentation you pointed out:

In order to select attributes starting with tags. a metric name has to be provided. For example, SELECT uniques(tags.environment) FROM Metric WHERE metricName=’aws.lambda.function.duration’ does not work without the WHERE clause.

Hence I turned this into:

FROM Metric SELECT max(k8s.container.cpuUsedCores) AS 'Used', min(k8s.container.cpuRequestedCores) AS 'Requested', min(k8s.container.cpuLimitCores) AS 'Limit' WHERE metricName IN ('k8s.container.cpuUsedCores', 'k8s.container.cpuRequestedCores', 'k8s.container.cpuLimitCores') AND k8s.namespaceName='...' AND k8s.containerName='...' AND tags.app='...' TIMESERIES

But that still shows the same :warning: and tooltip.

@dschridde Following up to see if you are still seeing the warning sign. Sorry that our support team hasn’t been able to look into this further for you yet.