Data Dictionary for New Relic

New Relic's own data dictionary, kept here: every event type New Relic defines, the agent or product that sends it, and what each attribute on it means. It is the reference for telling New Relic's own data from what an account sends itself. Anyone signed in can read it.

What is in it

Event types lists each one with its data source, such as APM, Browser agent, Infrastructure, Kubernetes, Mobile or Synthetics, how many attributes it has and what it is. Narrow the list by data source or by name. Click an event type for its attributes: each with its units, what it means, and the other event types that carry the same attribute.

Attributes searches every attribute by name, across all event types, and says which event types each is on. Click one of those to open it.

An event type that is not listed is the account's own data, such as a custom event, or belongs to a product New Relic has not written up in its dictionary. Logs and the names of individual metrics are not in it: the dictionary describes event types and their attributes.

Agent source

The dictionary is what the other screens use to say where data comes from, under the label Agent source.

• Ingest Analysis. Each data source in an account's breakdown carries its agent source: the New Relic agent or product that sends it, such as APM, Browser agent, Infrastructure or Mobile, taken from the event types that kind of ingest is made of. Logs and metrics read Mixed, because they arrive from agents, forwarders and other senders alike, and custom events read Not New Relic. The variance analysis page says the same under its title, and where it breaks ingest down by event type, each event type is marked: New Relic's own with the agent that sends it, anything else as Not New Relic.
• Metrics Validator and Log Validator. The Agent source column says what sent each metric or shipped each stream, read from the data itself. Those sent by a New Relic agent, or generated by New Relic, are marked in green; OpenTelemetry, Prometheus, log forwarders and the APIs are named plainly.

Green means New Relic's own agent or product. It is a statement of where the data comes from, not of whether it is needed.

Where it comes from

The dictionary is read from New Relic's API, which is where New Relic's own documentation page gets it, and the copy kept here is brought up to date once a week. It is one copy, shared by every organization, since it is the same for all of them. A copy ships with the application, so the screen works before the first update. The line under the title says which copy is showing and when it was taken. Update from New Relic, for admins, fetches it again now.