Log event data | New Relic Documentation

Log events are records stored like any other event sent to New Relic. At a minimum the record should include:

timestamp: an integer representing Unix epoch milliseconds
At least one attribute containing data, like a message field

Typically logs have a message field and level or severity, but we do not have fixed requirements for what you can send to New Relic.

Data storage

Log records are stored by default in the Log event type. You can create additional event types by defining a custom data partition in our Logs UI. The resulting types will always be prefaced with Log_. For detailed information, see our data partitions documentation.

Attributes:

Maximum attributes: 255
Name: maximum 255 characters
Searchable value: The first 4,094 characters of data stored in an attribute can be queried directly in the UI.

Additional storage:

Any attribute with more than 4,094 characters will have up to 128KB of data stored in a "blob" in the New Relic backend.
Blob storage is not searchable, but you can access data stored in blobs in the New Relic One UI.
Data beyond 128KB will be truncated.

Restrictions

Some specific attributes have additional restrictions:

Attribute	Restrictions
`accountId`	This is a reserved attribute name. If it is included, it will be dropped during ingest.
`eventType`	This is a reserved attribute name. If it is included, it will be dropped during ingest.
`entity.guid` `entity.name` `entity.type`	These attributes are used internally to identify entities. Any values submitted with these keys in the attributes section of a metric data point may cause undefined behavior such as missing entities in the UI or telemetry not associating with the expected entities. For more information, see our documentation about entity synthesis.
`timestamp`	This value must be an integer representing milliseconds since Unix epoch. Seconds since epoch is also supported. Payloads with timestamps older than 48 hours may be dropped.