This feature is currently in beta.
Dimensional metrics are an industry standard for storing and querying metric data. All infrastructure metrics are stored as event data in New Relic, but you can also query them through dimensional metrics.
In this page you can learn:
This type of metric enables you to:
- Enjoy an improved query experience for Infrastructure data.
- Discover all your metrics in one place.
- Tap into more metric sources, such as Prometheus.
For example, the query to get the maximum duration of your Lambda functions is simplified:
Query with samples
Query with metrics
No agent or integration updates are required to use these metrics.
NRQL alerting based on dimensional metrics is also supported, except for data coming from cloud integrations (that is metrics from AWS polling integrations, GCP, and Azure). AWS CloudWatch Metric Streams metrics are ingested as dimensional metrics and NRQL alerts are recommended.
All current NRQL query features are supported. Queries can use
FACET, and time selection functions such as
All metric names and attributes for dimensional metrics follow the same naming convention in order to make them easy to find and use. Metric and attribute names are namespaced with dots: for example, the
host. prefix is used for host metrics, the
k8s. prefix is used for Kubernetes metrics, and
aws. is used for AWS metrics.
The graphic below shows how a
ProcessSample that contains three metrics (
ioTotalWriteBytes) is split into three separate metrics. Note the updated naming of the metrics and the attributes.
Dimensional metrics naming convention
Here are some examples of NQRL queries with and without dimensional metrics:
- Metric queries with
*do not return Infrastructure sample data (for example,
SELECT * FROM Metric).
- 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
- Results may not be complete if the selection criteria matches too many samples. For example,
SELECT uniqueCount(entity.guid) FROM Metricmaps to all Infrastructure samples, and may return incomplete results.
- Initially there is no support for the newly introduced metric wildcarding feature (for example,
SELECT average(host.swap%Bytes) FROM Metric).