Service Fieldsedit

The service fields describe the service for or from which the data was collected.

These fields help you find and correlate logs for a specific service and version.

Service Field Detailsedit

Field Description Level


Address where data about this service was collected from.

This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets).

type: keyword




[beta] This field is beta and subject to change.

Identifies the environment where the service is running.

If the same service runs in different environments (production, staging, QA, development, etc.), the environment can identify other instances of the same service. Can also group services and applications from the same environment.

type: keyword

example: production



Ephemeral identifier of this service (if one exists).

This id normally changes across restarts, but does not.

type: keyword

example: 8a4f500f


Unique identifier of the running service. If the service is comprised of many nodes, the should be the same for all nodes.

This id should uniquely identify the service. This makes it possible to correlate logs and metrics for one specific service, no matter which particular node emitted the event.

Note that if you need to see the events from one specific host of the service, you should filter on that or instead.

type: keyword

example: d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6


Name of the service data is collected from.

The name of the service is normally user given. This allows for distributed services that run on multiple hosts to correlate the related instances based on the name.

In the case of Elasticsearch the could contain the cluster name. For Beats the is by default a copy of the service.type field if no name is specified.

type: keyword

example: elasticsearch-metrics


Name of a service node.

This allows for two nodes of the same service running on the same host to be differentiated. Therefore, should typically be unique across nodes of a given service.

In the case of Elasticsearch, the could contain the unique node name within the Elasticsearch cluster. In cases where the service doesn’t have the concept of a node name, the host name or container name can be used to distinguish running instances that make up this service. If those do not provide uniqueness (e.g. multiple instances of the service running on the same host) - the node name can be manually set.

type: keyword

example: instance-0000000016



Deprecated for removal in next major version release. This field will be superseded by node.roles.

Role of a service node.

This allows for distinction between different running roles of the same service.

In the case of Kibana, the service.node.role could be ui or background-tasks.

In the case of Elasticsearch, the service.node.role could be master or data.

Other services could use this to distinguish between a web and worker role running as part of the service.

type: keyword

example: background-tasks



Current state of the service.

type: keyword



The type of the service data is collected from.

The type can be used to group and correlate logs and metrics from one service type.

Example: If logs or metrics are collected from Elasticsearch, service.type would be elasticsearch.

type: keyword

example: elasticsearch



Version of the service the data was collected from.

This allows to look at a data set only for a specific version of a service.

type: keyword

example: 3.2.4


Field Reuseedit

The service fields are expected to be nested at:

  • service.origin

Note also that the service fields may be used directly at the root of the events.

Field sets that can be nested under Serviceedit
Location Field Set Description



[beta] Reusing the service fields in this location is currently considered beta.

Describes the origin service in case of an incoming request or event.*


[beta] Reusing the service fields in this location is currently considered beta.

Describes the target service in case of an outgoing request or event.

Service Field Usageedit

For usage and examples of the service fields, please see the Service Fields Usage and Examples section.