The following attributes are grouped into a few functional domains:
- Syslog and log shippers
- Network communications
- HTTP Requests
- Source code
- Infrastructure metrics
- User related attributes
Related to the data added by a syslog or a log-shipper agent. All fields and metrics are prefixed by
The hostname related to the log event
The application name (or tag) related to the log event
The level of the severity of the log event
The environment name where the source of logs come from
Some integrations that rely on these are: Rsyslog, NxLog, Syslog-ng, Infrastructure, Fluentd, Logstash, etc.
Related to the data used in a network communication. All fields and metrics are prefixed by
The IP address of the client which initiated the TCP connection
The IP address the client connected to
The port of the client which initiated the connection.
The TCP port the client connected to
Total number of bytes transmitted from the client to the server when the log is emitted
Total number of bytes transmitted from the server to the client when the log is emitted
Integrations using it: Apache, Varnish, AWS ElasticBalancer, Nginx, etc.
Related to the data commonly used in HTTP requests & accesses. All attributes are prefixed by
The HTTP request
Total time in milliseconds elapsed for the processing of the request
The HTTP status code returned to the client
The HTTP verb of the request
Url that the client reports having been referred from
The HTTP referer
The HTTP request id
The User-Agent as it is sent (raw format). See bellow for all details about it
The HTTP host part of the request
The HTTP port part of the request
The HTTP path part of the request
The HTTP query string part of the request
The OS family reported by the user-agent
The Browser Family reported by the user-agent
The Device family reported by the user-agent
Integrations relying on these attributes are: Apache, Rails, AWS CloudFront, NodeJs, etc.
Related to the data used when log and error are shipped via a logger. All attributes are prefixed either by
The name of the logger
The name of the current thread when the log is fired
The class method name
The error name
The code error
The stack trace or the complementary information about the error
Integrations relying on these attributes are: Java Log4J, NodeJs, Goland, Source code, etc.
Related to the OS metrics. All attributes are prefixed by
The total of memory
The resident set size used
The cache size used
The size of the swap used
The percent of cpu used
Integrations using it: Docker, Infrastructure, PerfStats, Elastic Beats etc.
Related to the data used when the application is logging data about the current context.
All fields and metrics are prefixed by
The fullname of the user attached to the event
The user's email attached to the event