New Relic data dictionary

The ID of your application, as recorded by New Relic.

The name of the application that handled the request as shown in New Relic Browser.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.

The latitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's latitude.

The longitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's longitude.

The organization that owns the Autonomous System Number. Often an ISP, sometimes a private company or institution.

A unique value generated for each browser interaction captured by the New Relic agent.

The name of the interaction. This is either the targetGroupedUrl or the custom name set via the API.

The city in which the event occurred, such as Portland or Seattle.

The country from which the browser initiated the page load. For a list of country codes, see ISO 3166-1 alpha-2.

The type of device that loaded the page: mobile, tablet, or desktop.

A value that you can link to multiple BrowserInteraction events so you can view the interactions that occurred surrounding a specific event. For example, you can see the browser interactions that occurred prior to a JS error.

The grouped URL of the view that made the AJAX request. For example: myapp.com/acct/*/dash.

The grouped URL of the AJAX request. For example: myapp.com/acct/*/ajax.

The fully qualified domain name (FQDN) of the request URL.

The HTTP method of the AJAX request. Example: POST.

The HTTP response code. Example: 200.

The total duration, in seconds, spent on JavaScript execution. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction. This attribute doesn't exist for initial page load events.

The URL of the page that was loaded for the PageView. For example: http://www.newrelic.com. This URL does not include query parameters.

A unique value generated for each interaction with the page. You can use this value to group interactions together.

The request port.

Likelihood this event will be saved.

The specific administrative division within a country where the PageView event occurred. In the United States, regions correspond to state codes, such as WA or NY. Outside the United States, a country's regions correspond to numerical codes.

In the United States, regions correspond to state codes ; for example, WA or NY. Outside the United States, a country's regions correspond to numerical codes .

The payload size of the request body, in bytes.

The URL of the AJAX request. For example: myapp.com/acct/1/ajax.

The payload size of the response body, in bytes.

A unique identifier for a single session. The session cookie expires when the user closes the browser (for example, they fully exit Chrome.) A new session identifier will be assigned when the user opens up a new instance of the browser.

The time in seconds between the start of the BrowserInteraction and the start of the request.

The duration, in seconds, from the start of the request (timestamp) to the end of the last callback. This is not just an additive function; the callback time can overlap with the wait time. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction.

The time, in seconds, from the start of the AJAX request to the start of its load event. This value represents the duration of the AJAX request with single page app (SPA) monitoring.

For more information, see the Mozilla developer documentation about XMLHttpRequest load events.

The time, in seconds, from the start of the request to when all resulting callbacks (including callbacks of subsequent AJAX requests) are complete. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction.

The time (date, hour, minute, second) at which the interaction occurred.

The browser’s name, such as Chrome and Firefox, obtained from the User-Agent header of an HTTP request.

The browser’s reported operating system, such as Windows or Linux, that it is running on. This is obtained from the User-Agent header of an HTTP request.

The browser’s reported software version, which is obtained from the User-Agent header of an HTTP request.

The Amazon Resource Name (ARN) of the instrumented Lambda function.

A Boolean indicating if the AWS Lambda invocation is a cold start.

The Amazon Resource Name (ARN) of the entity that invoked the instrumented Lambda function.

AWS identifier of the invocation.

The number of database calls made by this transaction.

The database response time in seconds.

The total invocation time for the transaction, in seconds. (Data source: AWS Lambda)

The number of external calls made by this transaction.

The total response time of all external (out-of-process) services, in seconds.

Where the data point entered the platform (such as browser.spans, or api.traces).

If a distributed tracing payload is received, this is the account identifier for the transaction's upstream caller.

If a distributed tracing payload is received, this is the application identifier. APM agents retrieve this value in the connect response under the key primary_application_id.

When a distributed tracing payload is received, the method of transport for the payload. Example values: Unknown, HTTP, HTTPS, Kafka, JMS, IronMQ, AMQP, Queue, or Other.

If a distributed trace payload was received, the parent's data source type. Example values: App, Browser, Mobile.

The types as read from the HTTP Accept request header.

Incoming request size in bytes as read from the Content-Length HTTP request header.

Incoming request content-type as read from the HTTP request header Content-Type. Example value: application/octet-stream.

The name from the HTTP host request header.

The incoming request referer as read from the Referer request header.

The contents of the User-Agent HTTP header.

The HTTP request method used. Example values: POST, GET.

The outgoing response size in bytes as read from the Content-Length response header.

For an HTTP response, the data type of the returned response. Example values: text/html, application/json.

The response code for an HTTP request

The sum of all async components' duration, in seconds. An async component is a method or function where there is no instrumented encapsulating method or function.

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.

The New Relic event type. Example values: Transaction, Span.

The Amazon Resource Name (ARN) of the instrumented Lambda function.

A Boolean indicating if the AWS Lambda invocation is a cold start.

The Amazon Resource Name (ARN) of the entity that invoked the instrumented Lambda function.

AWS identifier of the invocation.

The number of database calls made by this transaction.

The database response time in seconds.

The total invocation time for the transaction, in seconds. (Data source: AWS Lambda)

The class name or type for the error. This will be server and platform specific.

The error message for the transaction. This will be server and platform specific.

The number of external calls made by this transaction.

The total response time of all external (out-of-process) services, in seconds.

Where the data point entered the platform (such as browser.spans, or api.traces).

If a distributed tracing payload is received, this is the account identifier for the transaction's upstream caller.

If a distributed tracing payload is received, this is the application identifier. APM agents retrieve this value in the connect response under the key primary_application_id.

When a distributed tracing payload is received, the method of transport for the payload. Example values: Unknown, HTTP, HTTPS, Kafka, JMS, IronMQ, AMQP, Queue, or Other.

If a distributed trace payload was received, the parent's data source type. Example values: App, Browser, Mobile.

The types as read from the HTTP Accept request header.

Incoming request size in bytes as read from the Content-Length HTTP request header.

Incoming request content-type as read from the HTTP request header Content-Type. Example value: application/octet-stream.

The name from the HTTP host request header.

The incoming request referer as read from the Referer request header.

The contents of the User-Agent HTTP header.

The HTTP request method used. Example values: POST, GET.

The outgoing response size in bytes as read from the Content-Length response header.

For an HTTP response, the data type of the returned response. Example values: text/html, application/json.

The error stack trace. The format will be different depending on the agent language.

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.

Name of the transaction in which the error occurred. Example value: Controller/customers/show. Value may be 'Unknown' if an error occurs outside of a transaction.

The New Relic event type. Example values: Transaction, Span.

The text of the HTML element that was clicked when a browser interaction started.

A count of all XHRs included in the timing of a SPA interaction.

The ID of your application, as recorded by New Relic.

The name of the application that handled the request as shown in New Relic Browser.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.

The latitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's latitude.

The longitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's longitude.

The organization that owns the Autonomous System Number. Often an ISP, sometimes a private company or institution.

The name of the backend transaction that served the initial page load.

A unique value generated for each browser interaction captured by the New Relic agent.

The name of the interaction. This is either the targetGroupedUrl or the custom name set via the API.

The type of interaction; either initial page load, route change, or custom.

The city in which the event occurred, such as Portland or Seattle.

The country from which the browser initiated the page load. For a list of country codes, see ISO 3166-1 alpha-2.

The type of device that loaded the page: mobile, tablet, or desktop.

The domain portion of the request URL.

The total time elapsed of the interaction event

A value that you can link to multiple BrowserInteraction events so you can view the interactions that occurred surrounding a specific event. For example, you can see the browser interactions that occurred prior to a JS error.

firstContentfulPaint is the point when the browser renders the first bit of content from the DOM, which may be text, an image, SVG, or a <canvas> element.

Google's User-centric Performance Metrics contains detailed information about its Paint Timing API and firstContentfulPaint.

See Compatibility and requirements for New Relic Browser for additional information about firstContentfulPaint browser compatibility.

firstPaint marks the point when the browser renders anything that is visually different from what was on the screen prior to navigation. This includes non-default background paint and the enclosing box of an iframe.

Google's User-centric Performance Metrics contains detailed information about its Paint Timing API and firstPaint.

See Compatibility and requirements for New Relic Browser for additional information about firstPaint browser compatibility.

The total duration, in seconds, spent on JavaScript execution. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction. This attribute doesn't exist for initial page load events.

The Synthetics account from which you are running the monitor.

A unique number identifying a particular monitor.

The ID of a single Synthetics monitor run, which began at a specific time and originated from a specific location.

A unique value generated for each interaction with the page. You can use this value to group interactions together.

The grouped version of the URL in the browser at the start of the interaction.

The route name of the page at the start of the interaction. This is the last value passed by setCurrentRouteName before the start of the interaction.

The ungrouped URL in the browser at the start of the interaction.

The specific administrative division within a country where the PageView event occurred. In the United States, regions correspond to state codes, such as WA or NY. Outside the United States, a country's regions correspond to numerical codes.

In the United States, regions correspond to state codes ; for example, WA or NY. Outside the United States, a country's regions correspond to numerical codes .

A unique identifier for a single session. The session cookie expires when the user closes the browser (for example, they fully exit Chrome.) A new session identifier will be assigned when the user opens up a new instance of the browser.

The grouped version of the URL in the browser at the end of the interaction.

The route name for the page at the end of the interaction. The last value passed by setCurrentRouteName before the end of the interaction.

The ungrouped URL in the browser at the end of the interaction.

The time, in seconds, from the start of the interaction to the connectEnd, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the connectStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domComplete, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domContentLoadedEventEnd, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domContentLoadedEventStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domInteractive, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domLoading, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domainLookupEnd, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the domainLookupStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the fetchStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The duration, in seconds, from the start of the request (timestamp) to the end of the last callback. This is not just an additive function; the callback time can overlap with the wait time. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction.

The time, in seconds, from the start of the interaction to the loadEventEnd, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the loadEventStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information, see our documentation about instrumentation for the Navigation Timing API.

The time, in seconds, from the start of the interaction to the redirectEnd, as defined by the Navigation Timing API. This attribute exists only for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the redirectStart, as defined by the Navigation Timing API. This attribute exists only for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the requestStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the responseEnd, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the responseStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the secureConnectionStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the unloadEventEnd, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time, in seconds, from the start of the interaction to the unloadEventStart, as defined by the Navigation Timing API. This attribute exists for initial page load events, not route changes.

For more information about the Navigation Timing API, see Instrumentation for Browser monitoring.

The time (date, hour, minute, second) at which the interaction occurred.

The cause of the route change or page load. The default values are click, submit, popstate, or initial page load. For a custom event created with the API, the default value for trigger will be api. This value can also be set via the API.

The browser’s name, such as Chrome and Firefox, obtained from the User-Agent header of an HTTP request.

The browser’s reported operating system, such as Windows or Linux, that it is running on. This is obtained from the User-Agent header of an HTTP request.

The browser’s reported software version, which is obtained from the User-Agent header of an HTTP request.

The ID of your application, as recorded by New Relic.

The name of the application that handled the request as shown in New Relic Browser.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.

The latitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's latitude.

The longitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's longitude.

The organization that owns the Autonomous System Number. Often an ISP, sometimes a private company or institution.

A unique value generated for each browser interaction captured by the New Relic agent.

The name of the interaction. This is either the targetGroupedUrl or the custom name set via the API.

The name of the event. This is taken from the name argument of createTracer.

The city in which the event occurred, such as Portland or Seattle.

The country from which the browser initiated the page load. For a list of country codes, see ISO 3166-1 alpha-2.

The type of device that loaded the page: mobile, tablet, or desktop.

A value that you can link to multiple BrowserInteraction events so you can view the interactions that occurred surrounding a specific event. For example, you can see the browser interactions that occurred prior to a JS error.

The grouped URL of the view that made the AJAX request. For example: myapp.com/acct/*/dash.

The total duration, in seconds, spent on JavaScript execution. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction. This attribute doesn't exist for initial page load events.

The URL of the page that was loaded for the PageView. For example: http://www.newrelic.com. This URL does not include query parameters.

A unique value generated for each interaction with the page. You can use this value to group interactions together.

The specific administrative division within a country where the PageView event occurred. In the United States, regions correspond to state codes, such as WA or NY. Outside the United States, a country's regions correspond to numerical codes.

In the United States, regions correspond to state codes ; for example, WA or NY. Outside the United States, a country's regions correspond to numerical codes .

A unique identifier for a single session. The session cookie expires when the user closes the browser (for example, they fully exit Chrome.) A new session identifier will be assigned when the user opens up a new instance of the browser.

The time in seconds between the start of the BrowserInteraction and the start of the request.

The duration, in seconds, from the start of the request (timestamp) to the end of the last callback. This is not just an additive function; the callback time can overlap with the wait time. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction.

The time, in seconds, from the start of the request to when all resulting callbacks (including callbacks of subsequent AJAX requests) are complete. This attribute is only seen in AjaxRequest data that is tied to BrowserInteraction.

The time in seconds from the start of the custom tracer until the start of the traced callback. This attribute is unique to the BrowserTiming event.

The time (date, hour, minute, second) at which the interaction occurred.

The duration in seconds of the traced callback. This attribute is unique to the BrowserTiming event.

The browser’s name, such as Chrome and Firefox, obtained from the User-Agent header of an HTTP request.

The browser’s reported operating system, such as Windows or Linux, that it is running on. This is obtained from the User-Agent header of an HTTP request.

The browser’s reported software version, which is obtained from the User-Agent header of an HTTP request.

Data space available in the Storage Driver. Only Device Mapper driver is supported.

Total Data space in the Storage Driver. Only Device Mapper driver is supported.

Percent of Data space used in the Storage Driver. Only Device Mapper driver is supported.

Data space used by the Storage Driver. Only Device Mapper driver is supported.

Metadata space available in the Storage Driver. Only Device Mapper driver is supported.

Total Metadata space in the Storage Driver. Only Device Mapper driver is supported.

Percent of Metadata space used in the Storage Driver. Only Device Mapper driver is supported.

Metadata space used by the Storage Driver. Only Device Mapper driver is supported.

The command line used in the container.

The unique Docker container ID.

CPU time percentage used in kernel space.

Number of cores available for the container.

CPU usage percentage used.

Number of CPU shares assigned to the container.

Total number of periods throttled.

Total throttling time in milliseconds.

CPU usage per core.

CPU usage percentage per core.

CPU time percentage used in user space.

The number of times that alert conditions violated critical thresholds, causing critical violations and opening incidents. If this attribute does not exist on the sample, it has zero violations.

The Docker image ID for the image the container is based on.

The Docker image name for the container.

Docker labels associated with this container (where KEY represents a custom label's key value).

The amount of memory used by the container that can be associated precisely with a block on a block device.

The amount of current kernel memory allocation.

The amount of memory that doesn't correspond to anything on disk: stacks, heaps, and anonymous memory maps.

The total amount of memory the container is allowed to use.

The soft limit of memory usage equivalent to the memory reservation of the container.

The total amount of memory the container is using, including swap.

This metric is calculated as the percentage of memorySwapUsageBytes over memorySwapLimitBytes, if the limit exists.

The amount of swap memory the container is using. This memory doesn't include non-swap memory.

The amount of memory swap the container is using, including swap.

This metric doesn't account for swap usage.

This metric is calculated as the memoryUsageBytes percentage over memorySizeLimitBytes, if the limit exists.

The Docker container name.

Total number of received bytes.

Number of received bytes per second.

Total number of received packets dropped.

Number of received packets dropped per second.

Total number of received packets with error.

Number of received packets with error per second.

Total number of received packets.

Number of received packets with error per second.

Number of transmitted bytes per second.

Total number of transmitted packets dropped.

Number of transmitted packets dropped per second.

Total number of transmitted packets with error.

Number of transmitted packets with error per second.

Total number of transmitted packets.

Number of transmitted packets per second.

Total number of bytes transmitted.

The number of times the container was restarted.

It can be: created, restarting, running, removing, paused, exited, or dead.

Holds the current container state.

The number of times that alert conditions violated warning thresholds, causing warning violations.

A comma delimited list of newrelic accountIds that took part in this trace.

The total elapsed time in milliseconds of all backend services in this trace.

The timestamp of the first span in this trace from a backend entity. In distributed tracing, any events that are not from client-side applications contributed to the backend duration.

The duration of the entire distributed trace, including both backend and client-side entities. the earliest span to the latest.

The number of unique entities that took part in this trace.

A comma delimited list of entity GUIDs for entities that participated in this trace. These GUIDs are assigned by New Relic for the New Relic-monitored entity (host, application, etc.). Each GUID is stored as a Base64 encoded value.

The number of events in this distributed trace that were identified as errors.

The name of the trace filter used by the Infinite Tracing trace observer to select this trace.

The New Relic account ID that the root entity of this trace reports data to.

The entity GUID associated with the root entity of this trace.

The name of the root entity of this trace.

The elapsed time in milliseconds of the root span of this trace. The root of a distributed trace is the first span, and will have a null value for parent.id.

The unique identifier of the root span of this trace. The root of a distributed trace is the first span, and it has a null value for parent.id.

The name of the root span of this trace.

The timestamp of the root span of this trace. The root of a distributed trace is the first span, and will have a null value for parent.id.

The number of events in this distributed trace. Events in a distributed trace can have several event types, including Span, Transaction, and TransactionError.

The timestamp of the root span in this distributed trace.

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.

A New Relic category used to organize events in the UI. For example: automation, notification, and service.

A simple classification of the type of change made to the entity: added, modified, or removed.

The fully specified name of the item that changed. This is constructed by taking the source and adding one or more additional path elements that uniquely identify the item that changed.

Delta refers to a recorded change in the system. The deltaId is a number used by New Relic to organize incoming inventory change data.

The unique ID of the event, generated by New Relic.

The type of infrastructure event. Each format type includes attributes that may be used to render the event in the UI.

The new agent status: disconnected or connected.

If a change is made to the entity, this attribute contains the new value of the inventory that was changed. This will have no value if no change has been made. The value will display approximately 4K bytes of data.

If a change is made to the entity, this attribute contains the old value of the inventory that was changed. This will be blank if no change has been made.

For integrations that use generic event types (like the DatastoreSample event), the provider value specifies the source of the data (the service, or a sub-category of data from that service).

Some Insights events are generic and are used by several integrations. For example, the DatastoreSample event is used by several integrations, including the AWS DynamoDB integration and the AWS RDS integration. In these cases, the provider attribute value represents the source of that attribute. This will usually be the service that data comes from or, for integrations that use several provider values, a certain sub-category of data from that service.

When a provider value is present for a generic event, that event will have additional integration-specific attributes attached to it.

Here’s an example of an Insights NRQL query that returns the attributes present for a DatastoreSample event reported by the AWS RDS integration:

SELECT * from DatastoreSample where provider = 'RdsDbCluster'

The fully specified origin of this inventory item. This is typically in the form category/plugin, where plugin is the generic word used for the tool that gathered this data.

A summary of the change that happened. Uses a human-friendly string, such as Agent disconnected.

The type of change to the violation: For example: open or closed.

The identification number for the reporting browser agent.

The name of the application that handled the request as shown in New Relic Browser.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.

The latitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's latitude.

The longitude of the geographic center of the postal code where the Autonomous System Network is registered. This is not the end user's longitude.

The organization that owns the Autonomous System Number. Often an ISP, sometimes a private company or institution.

A unique value generated for each browser interaction captured by the New Relic agent.

An unique identifier generated for a stack trace. The browserStackHash for a stack trace is different across different browsers. An identical stack trace will generate the same identifier.

The city in which the event occurred, such as Portland or Seattle.

The country from which the browser initiated the page load. For a list of country codes, see ISO 3166-1 alpha-2.

The type of device that loaded the page: mobile, tablet, or desktop.

The domain portion of the request URL.

The unique identifier of the monitor referenced in New Relic One.

The error type of the JavaScript Error object. Examples: ReferenceError, SyntaxError, and UncaughtException.

The error message that was delivered.

A value to indicate whether or not this was the first JS error in the session. Example: true.

The Synthetics account from which you are running the monitor.

A unique number identifying a particular monitor.

The ID of a single Synthetics monitor run, which began at a specific time and originated from a specific location.

The URL of the page that was loaded for the PageView. For example: http://www.newrelic.com. This URL does not include query parameters.

A unique value generated for each interaction with the page. You can use this value to group interactions together.

The specific administrative division within a country where the PageView event occurred. In the United States, regions correspond to state codes, such as WA or NY. Outside the United States, a country's regions correspond to numerical codes.

In the United States, regions correspond to state codes ; for example, WA or NY. Outside the United States, a country's regions correspond to numerical codes .

The releases in which the app was updated. Example: {\"jQuery\":\"v3.1.1\",\"multiverse\":\"96e9ac7\"}.

The URI of the requested resource.

A unique identifier for a single session. The session cookie expires when the user closes the browser (for example, they fully exit Chrome.) A new session identifier will be assigned when the user opens up a new instance of the browser.

A unique identifier generated by the Browser agent for a stack trace. The stackHash for a stack trace is the same across different browsers. An identical stack trace will generate the same identifier.

A collection of the active stack frames when the error occurred.

A compressed version of the stackTrace attribute.

The time that the error occurred, in Unix time.

The full metric name of the transaction in which the error occurred, or Unknown if the error occurs outside of a transaction.

The browser’s name, such as Chrome and Firefox, obtained from the User-Agent header of an HTTP request.

The browser’s reported operating system, such as Windows or Linux, that it is running on. This is obtained from the User-Agent header of an HTTP request.

The browser’s reported software version, which is obtained from the User-Agent header of an HTTP request.

The end of the time range associated with the metric, in Unix time, in milliseconds. This is calculated by adding the metric interval to the timestamp of the metric (timestamp + interval.ms).

The length of the time window.

Name of the metric.

The source of this data. For example: metricAPI.

The start time for the metric, in Unix time.

The type of data, either session or interaction.

For interaction category events only. This is the total time for the interaction to render on the device. In addition to render time, this usually includes all external calls associated with the interaction. Currently, this attribute is measured in seconds for Android devices and in milliseconds for iOS devices.

For interaction category events only. This is the label of the interaction associated with the event. It is by default assigned by New Relic. For example: ApplicationsListFragment or Display iOS_Example.MasterViewController.

For interaction category events only. The UTC based timestamp for when the event was sent to New Relic. This is different from the attribute ‘timestamp’, which is when the event began.

Indicates the technical build number of the app binary. As a developer, you can use this attribute to identify specific builds of your app.

A unique identifier for a monitored app, based on the app token. For example: 35091.

The name of the monitored app. For example: My Mobile App - iOS.

The mobile application license token.

The version number of the monitored app. For example: 2.2.9.

An identifier for the specific version of the app. For example: 1713477.

The processor architecture of the device. For example: armv7 or arm64.

The telecom owner of the ASN.

The unique string used to identify the application.

The network over which the app transferred data, such as Wi-Fi, Verizon, or Sprint.

The exception associated with the crash, if one is present. For example: java.lang.NullPointerException.

The New Relic-generated fingerprint used to uniquely identify the crash and other crashes identical to this one.

The file in which the crash occurred.

The message associated with the crash, if one is present.

The manufacturer of the device, such as Motorola or HTC.

The model number of the device, such as XT1039 or SM-G900F.

The device's name.

A unique identifier assigned at the time of app installation by New Relic. It is only reset if a user deletes and then reinstalls the app. For example: B8B0BC30-0235-11E4-9191-0800200C9A66. Dupliate of uuid.

Space available on the device, in bytes.

The client interactions with the application that led to the crash.

A boolean value indicating whether or not this was the first occurrence of the crash.

The last interaction before a crash or harvest event, if one is present.

The total amount of memory, in MB, used by the application. Updated every 60 seconds.

The model of the device. This is the same as the session-level deviceModel attribute.

The type of network that the device was on at the time of crash, such as wifi or LTE.

The version number of the agent running on the application. For example: 4.232.0. Duplicate of newRelicAgentVersion.

The ID for this instance of the crash.

The orientation of the device, such as landscape or portrait.

For Android only. The specific build of the Android OS.

The simplified version number of the app's host operating system, such as iOS 11, as compared to iOS 11.0.4.

The name of the app's host operating system, for example, iOS or Android.

The exact version number of the app's host operating system, such as iOS 11.0.4, as compared to iOS 11.

The parent process that launched the crashing process.

The parent identification number (PID) of the parent process.

The platform type of the mobile monitoring agent, such as native or Cordova.

The PID of the previously running process on the device.

The name of the previously running process.

The path to the binary.

The UTC timestamp for when the event was received by New Relic. (This is different from timestamp, which is when the MobileSession event began that crashed.)

For Android only. The Android Runtime version where the exception/crash was generated.

A boolean value indicating whether or not that session crashed.

A unique identifier for a single user session. A new sessionId is created each time the app is brought into the foreground.

A boolean value indicating whether or not the crash was properly symbolicated.

The time, in milliseconds, since the interaction before a crash event.

The array of build UUIDs for applications and libraries.

A unique identifier assigned by New Relic for a specific app on a particular device. It is only reset if a user deletes and then reinstalls the app. For example: B8B0BC30-0235-11E4-9191-0800200C9A66. Dupliate of deviceUuid.

Indicates the technical build number of the app binary. As a developer, you can use this attribute to identify specific builds of your app.

A unique identifier for a monitored app, based on the app token. For example: 35091.

The name of the monitored app. For example: My Mobile App - iOS.

The version number of the monitored app. For example: 2.2.9.

An identifier for the specific version of the app. For example: 1713477.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.

The telecom owner of the ASN.

The network over which the app transferred data, such as Wi-Fi, Verizon, or Sprint.

The city in which the event occurred, such as Portland or Seattle.

The country from which the device ran the application. For a list of country codes, see ISO 3166-1 alpha-2.

The specific type of the device: iPhone 8, iPad Pro, etc. Duplicate of deviceType.

The manufacturer of the device, such as Motorola or HTC.

The model number of the device, such as XT1039 or SM-G900F.

The specific type of device: iPhone 8, iPad Pro, etc. Duplicate of device.

A unique identifier assigned at the time of app installation by New Relic. It is only reset if a user deletes and then reinstalls the app. For example: B8B0BC30-0235-11E4-9191-0800200C9A66. Dupliate of uuid.

The build uuid of the application binary in which the exception was caught.

The unsymbolicated, platform-specific cause of the exception.

New Relic defined location of an exception. Contains a combination of exception file name, class, line number, and method.

The class that generated the exception. Only present if symbolication succeeded.

The class that generated the exception. Only present if symbolication succeeded.

For XCFramework agent only. The library offset of the library that generated the exception. Only present if symbolication succeeded.

Comes from the exception: The line number where the exception was generated. Only present if symbolication succeeded.

The method that generated the exception. Only present if symbolication succeeded.

The unsymbolicated message from the exception. It can be user-generated or a generic system message. For Android, this is the Throwable message.

The unsymbolicated exception type.

The New Relic-generated identifier used to group like exceptions.

The unique ID of the exception event.

The last interaction before a crash or harvest event, if one is present.

For XCFramework agent only. The library name where the exception was generated.

For XCFramework agent only. The library start address where the exception was generated.

The total amount of memory, in MB, used by the application. Updated every 60 seconds.

The version number of the agent running on the application. For example: 4.232.0. Duplicate of newRelicAgentVersion.

Agent-reported epoch timestamp of the handled exception.

For Android only. The specific build of the Android OS.

The simplified version number of the app's host operating system, such as iOS 11, as compared to iOS 11.0.4.

The name of the app's host operating system, for example, iOS or Android.

The exact version number of the app's host operating system, such as iOS 11.0.4, as compared to iOS 11.

The platform type of the mobile monitoring agent, such as native or Cordova.

The specific region within a country where the monitored app is located. In the United States, regions are states. The regionCode is based on IP address and may not always match your region.

For Android only. The Android Runtime version where the exception/crash was generated.

A unique identifier for a single user session. A new sessionId is created each time the app is brought into the foreground.

Epoch timestamp of the handled exception. This exception timestamp represents the time New Relic created the event, if it's older than two days or some other unexpected time.

A unique identifier assigned by New Relic for a specific app on a particular device. It is only reset if a user deletes and then reinstalls the app. For example: B8B0BC30-0235-11E4-9191-0800200C9A66. Dupliate of deviceUuid.

Indicates the technical build number of the app binary. As a developer, you can use this attribute to identify specific builds of your app.

A unique identifier for a monitored app, based on the app token. For example: 35091.

The name of the monitored app. For example: My Mobile App - iOS.

The version number of the monitored app. For example: 2.2.9.

An identifier for the specific version of the app. For example: 1713477.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end user.

The telecom owner of the ASN.

Optional: If the application received a response from the requestUrl, the size of that response in bytes.

Optional: If the application sent a request to the requestUrl, the size of that request in bytes.

The network over which the app transferred data, such as Wi-Fi, Verizon, or Sprint.

The type of connection which the device was using, such as 2G or 3G.

The country from which the device ran the application. For a list of country codes, see ISO 3166-1 alpha-2.

The specific type of the device: iPhone 8, iPad Pro, etc. Duplicate of deviceType.

The category of the device, such as iPhone or Tablet.

The manufacturer of the device, such as Motorola or HTC.

The model number of the device, such as XT1039 or SM-G900F.

The display size of the device: Small, normal, large, xlarge.

The specific type of device: iPhone 8, iPad Pro, etc. Duplicate of device.

A unique identifier assigned at the time of app installation by New Relic. It is only reset if a user deletes and then reinstalls the app. For example: B8B0BC30-0235-11E4-9191-0800200C9A66. Dupliate of uuid.

Optional: The time to complete the request, measured in fractional seconds.

The unique identifier for the segment. This is equivalent to spanID in OpenTracing semantics.

The last interaction before a crash or harvest event, if one is present.

The total amount of memory, in MB, used by the application. Updated every 60 seconds.

The version number of the agent running on the application. For example: 4.232.0. Duplicate of newRelicAgentVersion.

The simplified version number of the app's host operating system, such as iOS 11, as compared to iOS 11.0.4.

The name of the app's host operating system, for example, iOS or Android.

The exact version number of the app's host operating system, such as iOS 11.0.4, as compared to iOS 11.

The platform type of the mobile monitoring agent, such as native or Cordova.

The specific region within a country where the monitored app is located. In the United States, regions are states. The regionCode is based on IP address and may not always match your region.

The domain that the application attempted to access when the event occurred.

The New Relic-generated identifier used to group like request events.

The REST method (GET, PUT, POST, etc.) that the application attempted when the event occurred.

The path that the application attempted to access when the event occurred.