Insights custom data requirements and limits

Total maximum size or length: 1 MB maximum per POST. We highly recommend using compression.

The Event API has additional HTTP rate limits.

Attribute values can be either a string or a numeric integer or float.

If your attribute values contain date information, define it as an unformatted Unix timestamp (in seconds or milliseconds) by using the Insights data formatter.

Maximum name size: 255 bytes.

Maximum attribute value size:

• Custom attributes sent by the agent: 255 bytes

• Attributes attached to custom events sent using the Event API: 4KB

  Insights charts only show the first 255 characters of attribute values. To read full attribute key/values, use the JSON chart type or Query API.

Maximum total attributes per event: 254. Exception: If you use the APM agent API, the max is 64. Maximum total attributes per event type: 48,000.

Attribute names can be a combination of alphanumeric characters, colons (:), periods (.), and underscores (_).

Event types (using the eventType attribute) can be a combination of alphanumeric characters, colons (:), and underscores (_).

Do not use words reserved for use by NRQL and Insights.

This is a reserved attribute name. If it is included, it will be dropped during ingest.

Value must be an integer. If it is not an integer, the attribute name and value will be dropped during ingest.

The event type as stored by New Relic Insights. New Relic agents and scripts normally report this as eventType. Can be a combination of alphanumeric characters, colons (:), and underscores (_). Be sure to review the prohibited eventType values and eventType limits.

For your eventType value, avoid using Metric, MetricRaw, and strings prefixed with Metric[0-9] (such as Metric2 or Metric1Minute). Events passed in with these event types will be dropped. These event types are reserved for use by New Relic.

Must be a Unix epoch timestamp. You can define timestamps either in seconds or in milliseconds. It must be +/-1 day (24 hours) of the current time on the server.

If you need to use NRQL syntax terms as attribute names, they must be enclosed in backticks; for example, `LIMIT`. Otherwise, avoid using these reserved words:

ago, and, as, auto,

begin, begintime,

compare,

day, days,

end, endtime, explain,

facet, from,

hour, hours,

in, is,

like, limit,

minute, minutes, month, months,

not, null,

offset, or,

raw,

second, seconds, select, since,

timeseries,

until,

week, weeks, where, with