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


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 if two instances of the same service are running on the same machine they can be differentiated by the

Also it 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



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