Service Fields
editService Fields
editThe 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 Details
edit| Field | Description | Level |
|---|---|---|
service.ephemeral_id |
Ephemeral identifier of this service (if one exists). This id normally changes across restarts, but type: keyword example: |
extended |
service.id |
Unique identifier of the running service. If the service is comprised of many nodes, the 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 type: keyword example: |
core |
service.name |
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 service.name could contain the cluster name. For Beats the service.name is by default a copy of the type: keyword example: |
core |
service.state |
Current state of the service. type: keyword |
core |
service.type |
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, type: keyword example: |
core |
service.version |
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: |
core |