Auto-telemetry with Pixie pulls data from the Pixie Cloud API and sends it to the New Relic OpenTelemetry endpoint. You can build your own charts and query your Auto-telemetry with Pixie data using the query builder and the NerdGraph API.
Find out more about getting started with Auto-telemetry with Pixie here.
Metrics and specifications
HTTP metrics
Query for duration of inbound HTTP request. For example:
FROM Metric SELECT average(http.server.duration)FACET service.nameWHERE instrumentation.provider='pixie'
Event type | Metric |
---|---|
Metric name |
|
Spec | |
Description | Measures the duration of the inbound HTTP request. |
OTEL data type |
|
Unit | milliseconds |
Required attributes |
|
Static attributes |
|
HTTP attributes |
|
Entity attributes |
|
JVM metrics
Query to measure the time spent in a given JVM garbage collectors in milliseconds. For example:
FROM Metric SELECT average(runtime.jvm.gc.collection) FACET service.name, gcWHERE instrumentation.provider='pixie'
Event type | Metric |
---|---|
Metric name |
|
Spec | |
Description | Time spent in a given JVM garbage collector in milliseconds. |
Unit | milliseconds |
Required attributes |
|
Static attributes |
|
JVM attributes | gc = |
Entity attributes |
|
Query to find out the number of bytes in a given JVM memory area. For example:
FROM Metric SELECT average(runtime.jvm.memory.area)FACET service.nameWHERE type='used' AND instrumentation.provider='pixie'
Event type | Metric |
---|---|
Metric name |
|
Spec | |
Description | Bytes of a given JVM memory area. |
Unit | bytes |
Required attributes |
|
Static attributes |
|
JVM attributes | type = |
Entity attributes |
|
HTTP server span
Example query:
FROM Span SELECT uniques(name)WHERE span.kind='server'AND instrumentation.provider='pixie'AND service.name='orders'
Spec | Semantic conventions for HTTP spans |
---|---|
Event type | Span |
Required attributes | name = |
Static attributes |
|
HTTP attributes |
|