New Relic event data dictionary

New Relic data sources (agents / products / services) generate data objects called events. Events contain key-value pairs called attributes.

This dictionary does not contain events reported by integrations. To learn about the data for integrations, see the integration documentation.

Displaying 1 - 30 of 30 results found

Event Types
Distributed Tracing
Span event

Span events are created when New Relic agents, or other tracing instrumentation tools, instrument operations that are part of a distributed trace. The operations that a span can represent include datastore queries, calls to other services, and method-level timing. For example, in an HTTP service, a span is created at the beginning of an HTTP request and completed when the HTTP server returns a response. Span attributes contain important information about the operation that the span represents (such as duration, host data, etc.), including trace state details (such as traceId, guid) that allow New Relic to connect spans together in a trace.

Total attributes in this event: 30

Attribute name Summary
appId The unique numeric identifier assigned by New Relic for the service/application where the transaction was created.
appName The application name set in the New Relic agent configuration.
asn Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.
category The type of span. Values include: generic, datastore, and http (external). The category type dictates UI display options (available charts, for example) and the collection of specific attributes.
component For 'datastore' category spans: the database vendor or driver, such as Redis and MySql. For 'external' category spans: the framework used to make the connection. For example: OkHttp and Net::HTTP.
containerId The container ID. The New Relic APM agent collects this when running in a containerized context.
db.instance The database name. For example, the name of the database for a given JDBC database connection URL in Java. Reported when the category is 'datastore.' Example value: dbc.url="jdbc:mysql://".
db.statement The database statement in the format most permissive by configuration. Reported when 'category' is 'datastore.' For a span with a 'component' of 'MySql', an example value would be: SELECT * FROM accounts.
duration The span's elapsed time in seconds. The span's elapsed time in milliseconds.
entityGuid The GUID, assigned by New Relic, for the New Relic-monitored entity (host, application, etc.). This value is stored as a Base64 encoded value.
error Makes a span as having an error.
error.class The full class name for the span's error.
error.message The message for the span's error.
guid The unique identifier for the segment. This is equivalent to spanID in OpenTracing semantics.
host The name of the application host that processed this request, as identified by the reporting agent. Examples: ip-10-1-34-88, ede2fff1efbe,
http.method The HTTP method or language method/function used for the call. Reported when the category is http. Examples: GET, POST.
http.url External URI for the call. Reported when 'category' is 'http.' It MUST NOT contain user, password, or query parameters. It MUST be set as an agent attribute and not as an intrinsic so that attribute filtering can be applied.
name The span name that best represents the operation.
parentId The span parent's GUID (may not be present for the root span).
peer.address The address of the datastore, including the host name and the port, path, or ID. Reported when 'category' is 'datastore.' Example:
peer.hostname The hostname of the database. Reported when 'category' is 'datastore.' Example:
priority A priority ranking that dictates whether the trace will be reported in situations where the sampling reservoir has exceeded capacity. This is a float value set by the first New Relic agent that’s part of the request.
realAgentId The ID of the New Relic agent that reported the data.
sampled Whether the request route was chosen to be sampled for tracing. The name of the instrumented service that created this span.
span.kind For spans that represent entry or exit into the process, this will be 'server' for entry or 'client' for exit. Datastore and external (http) spans will always have the value 'client.'
timestamp Unix timestamp in milliseconds indicating when the span started.
traceId The unique ID (a randomly generated string) used to identify a single request as it crosses inter- and intra- process boundaries. This ID allows the linking of spans in a distributed trace. Included when distributed tracing is enabled.
transactionId The GUID of the New Relic transaction associated with the span.