뉴렐릭 데이터 용어집

The text of the HTML element that was clicked when a browser interaction started. Added to BrowserInteraction and any AjaxRequest, JavaScriptError and BrowserTiming events that occurred during that interaction.

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

The name of the application that handled the request as shown in browser monitoring.

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 JavaScript 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 is tracked in browser storage using the Web Storage API, subject to each browser's implementation and handling. The session will automatically reset or refresh after a set period of inactivity or a pre-defined duration limit, whichever is less.

Allows for linking together end user actions from session traces and querying across browser events. Not all browser events will have this. For example, PageView events complete before the first session trace harvest. Also, initial page loads from BrowserInteraction won't always include this.

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

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

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 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. Added to BrowserInteraction and any AjaxRequest, JavaScriptError and BrowserTiming events that occurred during that interaction.

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 browser monitoring.

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 JavaScript 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 synthetic monitoring account from which you are running the monitor.

A unique number identifying a particular monitor.

The ID of a single synthetic 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 is tracked in browser storage using the Web Storage API, subject to each browser's implementation and handling. The session will automatically reset or refresh after a set period of inactivity or a pre-defined duration limit, whichever is less.

Allows for linking together end user actions from session traces and querying across browser events. Not all browser events will have this. For example, PageView events complete before the first session trace harvest. Also, initial page loads from BrowserInteraction won't always include this.

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 (date, hour, minute, second) at which the interaction occurred.

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 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 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 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 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 text of the HTML element that was clicked when a browser interaction started. Added to BrowserInteraction and any AjaxRequest, JavaScriptError and BrowserTiming events that occurred during that interaction.

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

The name of the application that handled the request as shown in browser monitoring.

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 JavaScript 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 is tracked in browser storage using the Web Storage API, subject to each browser's implementation and handling. The session will automatically reset or refresh after a set period of inactivity or a pre-defined duration limit, whichever is less.

Allows for linking together end user actions from session traces and querying across browser events. Not all browser events will have this. For example, PageView events complete before the first session trace harvest. Also, initial page loads from BrowserInteraction won't always include this.

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

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

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 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.

The command line used in the container.

The unique Docker container ID.

CPU time percentage used in kernel space.

How much of the available CPU resources a container can use.

CPU usage percentage used by CPU core. For containers with more than one CPU core, this percentage may be greater than 100%.

Number of CPU shares assigned to the container; increase or reduce the container's weight and give access to greater or lesser host machine CPU cycles. Weight may differ between cgroups v1 and cgroups v2.

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.

Total number of bytes transmitted.

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.

The number of times the container was restarted.

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

Holds the current container state.

Data space available in the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Total Data space in the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Percent of Data space used in the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Data space used by the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Metadata space available in the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Total Metadata space in the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Percent of Metadata space used in the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

Metadata space used by the Storage Driver. Only available while using Docker's devicemapper storage driver that is deprecated.

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

A URL for the changelog, or if it is not linkable, a list of changes.

The commit identifier (for example, the Git commit SHA).

A URL pointing back to the system generating the deployment. This field can hold any URL.

Unique identifier we generate when a marker is created. Alphanumeric IDs are from our newer NerdGraph change tracking feature. Numeric IDs are from our legacy REST API-based feature.

The type of the deployment (for example, 'BASIC', 'BLUE-GREEN', 'CANARY', 'OTHER', 'ROLLING', or 'SHADOW').

A description of the deployment.

The globally unique identifier for the New Relic entity that this marker applies to.

The friendly name for the New Relic entity this marker applies to.

String value that can be used to correlate multiple entities across a single change event.

The start time of the deployment (in milliseconds since Unix epoch).

Username of the deployer or bot that created this deployment.

The version of the deployment (for example, v1.1).

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.

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.

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

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 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 a 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 text of the HTML element that was clicked when a browser interaction started. Added to BrowserInteraction and any AjaxRequest, JavaScriptError and BrowserTiming events that occurred during that interaction.

The identification number for the reporting browser agent.

The name of the application that handled the request as shown in browser monitoring.

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 synthetic monitoring account from which you are running the monitor.

A unique number identifying a particular monitor.

The ID of a single synthetic 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 is tracked in browser storage using the Web Storage API, subject to each browser's implementation and handling. The session will automatically reset or refresh after a set period of inactivity or a pre-defined duration limit, whichever is less.

Allows for linking together end user actions from session traces and querying across browser events. Not all browser events will have this. For example, PageView events complete before the first session trace harvest. Also, initial page loads from BrowserInteraction won't always include this.

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.

Maximal number of currently used inflight request limit of the apiserver per request kind Mutating in the last second (requires k8s v1.23+).

Maximal number of currently used inflight request limit of the apiserver per request ReadOnly kind in the last second (requires k8s v1.23+).

This is a delta counter for each request verb (e.g. GET, WATCH, LIST, CREATE) and their response codes. The delta is between the current and the last polled value.

Rate of apiserver requests per minute, broken out for each verb and HTTP response code.

Number of stored objects at the time of last check, split by kind (requires k8s 1.23+; replaces etcdObjectCounts).

Number of stored objects at the time of last check, split by kind (alpha; deprecated in Kubernetes 1.22; replaced by apiserverStorageObjects).

Number of goroutines that currently exist.

Number of OS threads created.

Difference of the user and system CPU time spent, in seconds.

Resident memory size, in bytes.

Difference of the number of HTTP requests, partitioned by method and code.

Rate of the number of HTTP requests, partitioned by method and code.

Kubernetes version that the cluster is running on.

Name that you assigned to the cluster when you installed the Kubernetes integration.

Name that you assigned to the cluster when you installed the Kubernetes integration.

Delta change of elapsed enforcement period intervals.

Total number of elapsed enforcement period intervals.

Delta change of throttled period intervals.

Total number of throttled period intervals.

Delta change of duration the container has been throttled, in seconds.

Total time duration the container has been throttled, in seconds.

Unique ID associated with the container. If you are running Docker, this is the Docker container id.

Name of the image that the container is running.

Unique ID associated with the image that the container is running.

Total size of memory mapped files used by this container, in bytes.

Name associated with the container.

Number of "out of memory" events observed for the container (requires k8s v1.24+).

Percentage of CPU cores actually used by the container with respect to the CPU limit specified. This percentage is based on this calculation: (cpuUsedCores / cpuLimitCores) * 100.

Integer representing limit CPU cores defined for the container in the pod specification.

Requested CPU cores defined for the container in the pod specification.

CPU cores actually used by the container.

Name of the DaemonSet the container is associated with.

Name of the deployment to be used as an identifier.

Boolean. Whether or not the container's readiness check succeeded.

Name of the Job the container is associated with.

Labels associated with your container, so you can filter and query for specific containers. By default they are not collected, so you need to enable them in the KSM chart by configuring the metricLabelsAllowlist.

Integer representing limit bytes of memory defined for the container in the pod specification.

Integer. Requested bytes of memory defined for the container in the pod specification.

Integer. Bytes of memory actually used by the container.

Percentage of memory actually used by the container with respect to the memory limit specified.

Integer. Bytes of memory in the working set.

Percentage of working set memory actually used by the container with respect to the memory limit specified.

Name of the namespace that the container belongs to.

Host IP address the container is running on.

Host name that the pod is running on.

Name of the pod that the container is in, to be used as an identifier.

Provides a reason why the container is in the current status.

Name of the ReplicaSet the container is associated with.

Percentage of CPU cores actually used by the container with respect to the CPU request specified.

Percentage of memory actually used by the container with respect to the memory request specified.

Percentage of working set memory actually used by the container with respect to the memory request specified.

Number of times the container has been restarted.

Delta change of number of times the container has been restarted.

Name of the StatefulSet the container is associated with.

Current status of the container. Value can be Running, Terminated, or Unknown.

Number of goroutines that currently exist.

Number of OS threads created.

Gauge of if the reporting system is master of the relevant lease, 0 indicates backup, 1 indicates master.

Delta change of node evictions that happened since current instance of NodeController started (requires k8s v1.24+).

Difference of the user and system CPU time spent in seconds.

Resident memory size, in bytes.

Difference of the total number of adds handled by workqueue.

Current depth of workqueue.

Difference of the total number of retries handled by workqueue.

Whether or not to allow the jobs created by this CronJob to run concurrently.

Timestamp of when the CronJob was created.

The name of the CronJob.

Whether the CronJob has currently running jobs.

Whether the CronJob is currently suspended.

Labels associated with your CronJob so you can filter and query for specific CronJobs. By default they are not collected, so you need to enable them in the KSM chart by configuring the metricLabelsAllowlist.

The last time the CronJob successfully scheduled a job.

The resource version representing a specific version of the Cronjob.

Name of the namespace that the CronJob belongs to.

Next time the Cronjob should be scheduled. The time after lastScheduleTime, or after the Cronjob's creation time if it's never been scheduled. Use this to determine if the job is delayed.

The schedule which the CronJob uses to run jobs.

The deadline in seconds for starting the job if it misses scheduled time for any reason.

Name that you assigned to the cluster when you installed the Kubernetes integration.

Timestamp of when the DaemonSet was created.

Name associated with the DaemonSet.

Labels associated with your DaemonSet, so you can filter and query for specific DaemonSet. By default they are not collected, so you need to enable them in the KSM chart by configuring the metricLabelsAllowlist.

Sequence number representing a specific generation of the desired state.

Name of the namespace that the DaemonSet belongs to.

The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available.

The number of nodes that should be running the daemon pod.

The number of nodes running a daemon pod but are not supposed to.

Total number of replicas that are currently missing (number of desired replicas, podsDesired, minus the number of ready replicas, podsReady).

The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.

The number of nodes running at least one daemon pod and are supposed to.

The number of nodes that should be running the daemon pod and have none of the daemon pod running and available.

The total number of nodes that are running updated daemon pod.

Name that you assigned to the cluster when you installed the Kubernetes integration.

Timestamp of when the deployment was created.

Name of the deployment to be used as an identifier.

Labels associated with your deployment, so you can filter and query for specific deployments. By default they are not collected, so you need to enable them in the KSM chart by configuring the metricLabelsAllowlist.

Name of the namespace that the deployment belongs to.

Number of replicas that are currently available.

Number of replicas that you defined in the deployment.

Total number of replicas that are missing (number of desired replicas, podsDesired, minus the total number of replicas, podsTotal).

Total number of replicas that are currently running.

Number of replicas that are currently unavailable.

Number of replicas that have been updated to achieve the desired state of the deployment.

Number of addresses available in endpoint.

Number of addresses not ready in endpoint.

Name that you assigned to the cluster when you installed the Kubernetes integration.

Timestamp of when the endpoint was created.

Name associated with the endpoint.

Labels associated with your endpoint, so you can filter and query for specific endpoints. By default they are not collected, so you need to enable them in the KSM chart by configuring the metricLabelsAllowlist.

Name of the namespace that the endpoint belongs to.

Total size of the underlying database physically allocated, in bytes.

Rate of the total number of bytes received from gRPC clients.

Rate of the total number of bytes sent to gRPC clients.

Whether or not a leader exists. 1 is existence, 0 is not.

Difference of the number of leader changes seen.

Difference of the total number of consensus proposals applied.

Rate of the total number of consensus proposals applied.

Difference of the total number of consensus proposals committed.

Rate of the total number of consensus proposals committed.

Difference of the total number of failed proposals seen.