ECS::LogEntry::Service
Inherits JSON::Serializable < Struct < Value < Object
Constructors
Instance methods
service.ephemeral_id
Ephemeral identifier of this service (if one exists).
This id normally changes across restarts, but service.id does not.
Level: Extended Type: Keyword Example:
8a4f500f
service.ephemeral_id
Ephemeral identifier of this service (if one exists).
This id normally changes across restarts, but service.id does not.
Level: Extended Type: Keyword Example:
8a4f500f
service.id
Unique identifier of the running service. If the service is comprised of many
nodes, the service.id 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 host.name or host.id instead.
Level: Core Type: Keyword Example:
d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6
service.id
Unique identifier of the running service. If the service is comprised of many
nodes, the service.id 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 host.name or host.id instead.
Level: Core Type: Keyword Example:
d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6
service.name
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 service.name could contain the cluster name.
For Beats the service.name is by default a copy of the service.type field if
no name is specified.
Level: Core Type: Keyword Example:
elasticsearch-metrics
service.name
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 service.name could contain the cluster name.
For Beats the service.name is by default a copy of the service.type field if
no name is specified.
Level: Core Type: Keyword Example:
elasticsearch-metrics
service.state
Current state of the service.
Level: Core Type: Keyword
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, service.type
would be elasticsearch.
Level: Core Type: Keyword Example:
elasticsearch
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, service.type
would be elasticsearch.
Level: Core Type: Keyword Example:
elasticsearch
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.
Level: Core Type: Keyword Example:
3.2.4
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.
Level: Core Type: Keyword Example:
3.2.4