Skip to content

Commit

Permalink
chore: Update Attribute Dictionary JSON
Browse files Browse the repository at this point in the history
  • Loading branch information
@svc-docs-eng-opensource-bot
svc-docs-eng-opensource-bot committed Mar 25, 2024
1 parent 117ff5f commit f6044b3
Showing 1 changed file with 190 additions and 1 deletion.
191 changes: 190 additions & 1 deletion src/data/attribute-dictionary.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12461,6 +12461,195 @@
"definition": "<p>This event records usage every hour and is used to see usage reported per product.</p>\n",
"name": "NrUsage"
},
{
"attributes": [
{
"definition": "<p>The total time that it took for the query to execute.</p>\n",
"events": [
"NrdbQuery"
],
"name": "durationMs",
"units": {
"label": "milliseconds (ms)"
}
},
{
"definition": "<p>The number of events, if any, that were inspected while executing the query.</p>\n",
"events": [
"NrdbQuery"
],
"name": "inspectedCount",
"units": {
"label": "count"
}
},
{
"definition": "<p>The New Relic capability where the query originated.</p>\n",
"events": [
"NrdbQuery"
],
"name": "productCapability",
"units": {
"label": "enum"
}
},
{
"definition": "<p>The NRQL query string that was executed.</p>\n",
"events": [
"NrdbQuery"
],
"name": "query",
"units": null
},
{
"definition": "<p>The event type specified in the <code>FROM</code> clause of the query. A query with a <code>FROM</code> clause can return more than one event type.</p>\n",
"events": [
"NrdbQuery"
],
"name": "query.eventType",
"units": null
},
{
"definition": "<p>The count of data points scanned, if any, to return the query result.</p>\n",
"events": [
"NrdbQuery"
],
"name": "scannedEvents",
"units": {
"label": "count"
}
},
{
"definition": "<p>The API key used to execute the query for &#39;query-api&#39; sources.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.apiKeyId",
"units": {
"label": "ID"
}
},
{
"definition": "<p>The dashboard ID that executed this query for &#39;dashboard&#39; sources. This value can be entered into the <a href=\"/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#dashboards-search\">dashboard search bar</a> to display that dashboard.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.dashboardId",
"units": {
"label": "ID"
}
},
{
"definition": "<p>The Grafana dashboard where the query originated for &#39;prometheus-api&#39; sources.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.grafana.dashboardId",
"units": {
"label": "ID"
}
},
{
"definition": "<p>The panel on the Grafana dashboard where the query originated for &#39;prometheus-api&#39; sources.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.grafana.panelId",
"units": {
"label": "ID"
}
},
{
"definition": "<p>String description of the feature or tool the query originates from. Available values:</p>\n<ul>\n<li>apm: Application performance monitoring</li>\n<li>dashboard: Dashboards displayed on the New Relic platform</li>\n<li>Distributed tracing: Distributed tracing</li>\n<li>errors-inbox: Errors inbox</li>\n<li>infrastructure: Infrastructure monitoring</li>\n<li>metrics-explorer: Metrics explorer</li>\n<li>nerdgraph: NerdGraph, our GraphQL API</li>\n<li>nerdpack: A New Relic application or visualization</li>\n<li>New Relic user interface: A New Relic curated UI</li>\n<li>nrql-console: NRQL console</li>\n<li>prometheus-api: Queries via the Prometheus integration</li>\n<li>query-api: Insights query API</li>\n<li>query-builder: Query builder</li>\n<li>service-levels: Service levels</li>\n<li>other: Source not specified</li>\n</ul>\n",
"events": [
"NrdbQuery"
],
"name": "source.name",
"units": null
},
{
"definition": "<p>The unique identifier of the Nerdpack that executed the query, for &#39;nerdpack&#39; sources.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.nerdpackUuid",
"units": {
"label": "ID"
}
},
{
"definition": "<p>The PromQL query string that was translated into the NRQL query that was executed, for &#39;prometheus-api&#39; sources.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.promql.query",
"units": null
},
{
"definition": "<p>The URL of the UI page that executed this query.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.url",
"units": null
},
{
"definition": "<p>The ID of the dashboard widget that executed the query, for &#39;dashboard&#39; sources.</p>\n",
"events": [
"NrdbQuery"
],
"name": "source.widgetId",
"units": {
"label": "ID"
}
},
{
"definition": "<p>Indicates the successful or unsuccessful execution of the query. Available values:</p>\n<ul>\n<li><code>successful</code>: Query executed successfully.</li>\n<li><code>error</code>: Query failed to execute due to an error.</li>\n<li><code>cancelled</code>: Query execution stopped before fully completed.</li>\n<li><code>limited - congestion</code>: Query dropped due to internal New Relic system congestion.</li>\n<li><code>limited - inspected count</code>: Query dropped due to your account being over its inspected count resource limits.</li>\n<li><code>limited - memory estimation</code>: Query dropped as its estimated memory consumption exceeded system constraints. Reducing the complexity of this query could increase the probability of successful execution.</li>\n<li><code>limited</code>: Query dropped, no reason available.</li>\n<li><code>timedout</code>: Query timed out before execution completed and did not return results. Try reducing the scope of the query by changing the time window or reducing the number of EventTypes in the FROM clause.</li>\n</ul>\n",
"events": [
"NrdbQuery"
],
"name": "status",
"units": {
"label": "enum"
}
},
{
"definition": "<p>The difference in minutes between the <code>SINCE</code> and <code>UNTIL</code> clauses of the query. Often, the longer the time window, the longer the query will run and the more events will be inspected.</p>\n",
"events": [
"NrdbQuery"
],
"name": "timeWindowMinutes",
"units": {
"label": "minutes (min)"
}
},
{
"definition": "<p>The UNIX timestamp (milliseconds since epoch) of the date and time when the query was executed.</p>\n",
"events": [
"NrdbQuery"
],
"name": "timestamp",
"units": {
"label": "milliseconds (ms)"
}
},
{
"definition": "<p>The email address of the user who executed the query.</p>\n",
"events": [
"NrdbQuery"
],
"name": "user",
"units": null
}
],
"dataSources": [
{
"name": "Account Usage"
}
],
"definition": "<p>Each time a query is executed on behalf of a user in your account an NrdbQuery event is published. Events contain the full query string, information about when and where it originated, and how it performed.</p>\n",
"name": "NrdbQuery"
},
{
"attributes": [
{
Expand Down Expand Up @@ -13437,7 +13626,7 @@
}
},
{
"definition": "<p>An experimental metric that assesses responsiveness. A low INP means the page was consistently able to respond quickly to all or nearly all user interactions.</p>\n<p>For more information, see the <a href=\"https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics\"><code>PageViewTiming</code> documentation</a>.</p>\n",
"definition": "<p>A core web vitals metric that assesses responsiveness, or how quickly a web page visually responds to user actions like clicks or taps. A low INP means the page was consistently able to respond quickly to all or nearly all user interactions.</p>\n<p>For more information, see the <a href=\"https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/#interactivity-metrics\"><code>PageViewTiming</code> documentation</a>.</p>\n",
"events": [
"PageViewTiming"
],
Expand Down

0 comments on commit f6044b3

Please sign in to comment.