Collect logs and metrics from NATS servers with Elastic Agent.
What is an Elastic integration?
This integration is powered by Elastic Agent. Elastic Agent is a single, unified way to add monitoring for logs, metrics, and other types of data to a host. It can also protect hosts from security threats, query data from operating systems, forward data from remote services or hardware, and more. Refer to our documentation for a detailed comparison between Beats and Elastic Agent.
Prefer to use Beats for this use case? See Filebeat modules for logs or Metricbeat modules for metrics.
See the integrations quick start guides to get started:
This integration is used to collect logs and metrics from NATS servers. The integration collects metrics from NATS monitoring server APIs.
The Nats package is tested with Nats 1.3.0, 2.0.4 and 2.1.4
The log
dataset collects the NATS logs.
An example event for log
looks as following:
{
"nats": {
"log": {
"msg": {
"type": "payload"
},
"client": {
"id": "86"
}
}
},
"agent": {
"hostname": "5706c620a165",
"name": "5706c620a165",
"id": "25c804ef-d8c8-4a2e-9228-64213daef566",
"type": "filebeat",
"ephemeral_id": "4f1426bb-db10-4b5d-9e1c-ba6da401dc34",
"version": "7.11.0"
},
"process": {
"pid": 6
},
"log": {
"file": {
"path": "/var/log/nats/nats.log"
},
"offset": 36865655,
"level": "trace"
},
"elastic_agent": {
"id": "5a7b52c1-66ae-47ce-ad18-70dadf1bedfa",
"version": "7.11.0",
"snapshot": true
},
"network": {
"direction": "inbound"
},
"input": {
"type": "log"
},
"@timestamp": "2020-11-25T11:50:17.759Z",
"ecs": {
"version": "1.6.0"
},
"related": {
"ip": [
"192.168.192.3"
]
},
"data_stream": {
"namespace": "default",
"type": "logs",
"dataset": "nats.log"
},
"host": {
"hostname": "5706c620a165",
"os": {
"kernel": "4.9.184-linuxkit",
"codename": "Core",
"name": "CentOS Linux",
"family": "redhat",
"version": "7 (Core)",
"platform": "centos"
},
"containerized": true,
"ip": [
"192.168.192.8"
],
"name": "5706c620a165",
"id": "06c26569966fd125c15acac5d7feffb6",
"mac": [
"02:42:c0:a8:c0:08"
],
"architecture": "x86_64"
},
"client": {
"port": 53482,
"ip": "192.168.192.3"
},
"event": {
"ingested": "2020-11-25T11:53:10.021181400Z",
"created": "2020-11-25T11:53:04.192Z",
"kind": "event",
"type": [
"info"
],
"dataset": "nats.log"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
client.ip | IP address of the client (IPv4 or IPv6). | ip |
client.port | Port of the client. | long |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
error.message | Error message. | match_only_text |
event.created | event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent's or pipeline's ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used. | date |
event.dataset | Event dataset | constant_keyword |
event.kind | This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data coming in at a regular interval or not. | keyword |
event.module | Event module | constant_keyword |
event.type | This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types. | keyword |
input.type | Type of Filebeat input. | keyword |
log.file.path | Full path to the log file this event came from. | keyword |
log.level | Original log level of the log event. If the source of the event provides a log level or textual severity, this is the one that goes in log.level . If your source doesn't specify one, you may put your event transport's severity here (e.g. Syslog severity). Some examples are warn , err , i , informational . | keyword |
log.offset | Offset of the entry in the log file. | long |
message | For log events the message field contains the log message, optimized for viewing in a log viewer. For structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event. If multiple messages exist, they can be combined into one message. | match_only_text |
nats.log.client.id | The id of the client | integer |
nats.log.msg.bytes | Size of the payload in bytes | long |
nats.log.msg.error.message | Details about the error occurred | text |
nats.log.msg.max_messages | An optional number of messages to wait for before automatically unsubscribing | integer |
nats.log.msg.queue_group | The queue group which subscriber will join | text |
nats.log.msg.reply_to | The inbox subject on which the publisher is listening for responses | keyword |
nats.log.msg.sid | The unique alphanumeric subscription ID of the subject | integer |
nats.log.msg.subject | Subject name this message was received on | keyword |
nats.log.msg.type | The protocol message type | keyword |
network.direction | Direction of the network traffic. Recommended values are: * ingress * egress * inbound * outbound * internal * external * unknown When mapping events from a host-based monitoring context, populate this field from the host's point of view, using the values "ingress" or "egress". When mapping events from a network or perimeter-based monitoring context, populate this field from the point of view of the network perimeter, using the values "inbound", "outbound", "internal" or "external". Note that "internal" is not crossing perimeter boundaries, and is meant to describe communication between two hosts within the perimeter. Note also that "external" is meant to describe traffic between two hosts that are external to the perimeter. This could for example be useful for ISPs or VPN service providers. | keyword |
process.pid | Process id. | long |
related.ip | All of the IPs seen on your event. | ip |
tags | List of keywords used to tag each event. | keyword |
The default datasets are stats
, connections
, routes
and subscriptions
while connection
and route
datasets can be enabled to collect detailed metrics per connection/route.
This is the stats
dataset of the Nats package, in charge of retrieving generic
metrics from a Nats instance.
An example event for stats
looks as following:
{
"@timestamp": "2022-01-12T02:55:11.384Z",
"agent": {
"ephemeral_id": "259312b7-26e3-4a70-8c3a-720386a6a71e",
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"name": "docker-fleet-agent",
"type": "metricbeat",
"version": "8.0.0-beta1"
},
"data_stream": {
"dataset": "nats.stats",
"namespace": "ep",
"type": "metrics"
},
"ecs": {
"version": "1.12.0"
},
"elastic_agent": {
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"snapshot": false,
"version": "8.0.0-beta1"
},
"event": {
"agent_id_status": "verified",
"dataset": "nats.stats",
"duration": 49665904,
"ingested": "2022-01-12T02:55:14Z",
"module": "nats"
},
"host": {
"architecture": "x86_64",
"containerized": true,
"hostname": "docker-fleet-agent",
"id": "4ccba669f0df47fa3f57a9e4169ae7f1",
"ip": [
"172.18.0.4"
],
"mac": [
"02:42:ac:12:00:04"
],
"name": "docker-fleet-agent",
"os": {
"codename": "Core",
"family": "redhat",
"kernel": "5.11.0-44-generic",
"name": "CentOS Linux",
"platform": "centos",
"type": "linux",
"version": "7 (Core)"
}
},
"metricset": {
"name": "stats",
"period": 10000
},
"nats": {
"server": {
"id": "NCXFULRLCZMWAWXMVPHIAESOUAOURC2INJOQFODIMJ2IHZ3QE7BH7X74",
"time": "2022-01-12T02:55:11.384194105Z"
},
"stats": {
"cores": 1,
"cpu": 0.28,
"http": {
"req_stats": {
"uri": {
"connz": 0,
"root": 0,
"routez": 0,
"subsz": 0,
"varz": 2
}
}
},
"in": {
"bytes": 13072240,
"messages": 817015
},
"mem": {
"bytes": 12103680
},
"out": {
"bytes": 0,
"messages": 0
},
"remotes": 1,
"slow_consumers": 0,
"total_connections": 1,
"uptime": 23
}
},
"service": {
"address": "http://elastic-package-service-nats-1:8222/varz",
"type": "nats"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
event.dataset | Event dataset | constant_keyword |
event.module | Event module | constant_keyword |
nats.server.id | The server ID | keyword |
nats.server.time | Server time of metric creation | date |
nats.stats.cores | The number of logical cores the NATS process runs on | integer |
nats.stats.cpu | The current cpu usage of NATs process | scaled_float |
nats.stats.http.req_stats.uri.connz | The number of hits on connz monitoring uri | long |
nats.stats.http.req_stats.uri.root | The number of hits on root monitoring uri | long |
nats.stats.http.req_stats.uri.routez | The number of hits on routez monitoring uri | long |
nats.stats.http.req_stats.uri.subsz | The number of hits on subsz monitoring uri | long |
nats.stats.http.req_stats.uri.varz | The number of hits on varz monitoring uri | long |
nats.stats.in.bytes | The amount of incoming bytes | long |
nats.stats.in.messages | The amount of incoming messages | long |
nats.stats.mem.bytes | The current memory usage of NATS process | long |
nats.stats.out.bytes | The amount of outgoing bytes | long |
nats.stats.out.messages | The amount of outgoing messages | long |
nats.stats.remotes | The number of registered remotes | integer |
nats.stats.slow_consumers | The number of slow consumers currently on NATS | long |
nats.stats.total_connections | The number of totally created clients | long |
nats.stats.uptime | The period the server is up (sec) | long |
service.address | 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). | 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 . | keyword |
This is the connections
dataset of the Nats package, in charge of retrieving generic
metrics about connections from a Nats instance.
An example event for connections
looks as following:
{
"@timestamp": "2022-01-12T02:46:48.367Z",
"agent": {
"ephemeral_id": "3886806d-b880-4842-a4be-79391a8fc2e4",
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"name": "docker-fleet-agent",
"type": "metricbeat",
"version": "8.0.0-beta1"
},
"data_stream": {
"dataset": "nats.connections",
"namespace": "ep",
"type": "metrics"
},
"ecs": {
"version": "1.12.0"
},
"elastic_agent": {
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"snapshot": false,
"version": "8.0.0-beta1"
},
"event": {
"agent_id_status": "verified",
"dataset": "nats.connections",
"duration": 125128016,
"ingested": "2022-01-12T02:46:50Z",
"module": "nats"
},
"host": {
"architecture": "x86_64",
"containerized": true,
"hostname": "docker-fleet-agent",
"id": "4ccba669f0df47fa3f57a9e4169ae7f1",
"ip": [
"172.18.0.4"
],
"mac": [
"02:42:ac:12:00:04"
],
"name": "docker-fleet-agent",
"os": {
"codename": "Core",
"family": "redhat",
"kernel": "5.11.0-44-generic",
"name": "CentOS Linux",
"platform": "centos",
"type": "linux",
"version": "7 (Core)"
}
},
"metricset": {
"name": "connections",
"period": 10000
},
"nats": {
"connections": {
"total": 1
},
"server": {
"id": "NBBIEC4H2KI3XR4SUAATGL5INXZZS72ZUYMVJBCLKVDDEWCJCFZOXH7W",
"time": "2022-01-12T02:46:48.367495135Z"
}
},
"service": {
"address": "http://elastic-package-service-nats-1:8222/connz",
"type": "nats"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
event.dataset | Event dataset | constant_keyword |
event.module | Event module | constant_keyword |
nats.connections.total | The number of currently active clients | integer |
nats.server.id | The server ID | keyword |
nats.server.time | Server time of metric creation | date |
service.address | 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). | 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 . | keyword |
This is the routes
dataset of the Nats package, in charge of retrieving generic
metrics about routes from a Nats instance.
An example event for routes
looks as following:
{
"@timestamp": "2022-01-12T02:52:26.015Z",
"agent": {
"ephemeral_id": "5ca072d2-2eac-4cad-9a39-bdfec64f2640",
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"name": "docker-fleet-agent",
"type": "metricbeat",
"version": "8.0.0-beta1"
},
"data_stream": {
"dataset": "nats.routes",
"namespace": "ep",
"type": "metrics"
},
"ecs": {
"version": "1.12.0"
},
"elastic_agent": {
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"snapshot": false,
"version": "8.0.0-beta1"
},
"event": {
"agent_id_status": "verified",
"dataset": "nats.routes",
"duration": 29566227,
"ingested": "2022-01-12T02:52:29Z",
"module": "nats"
},
"host": {
"architecture": "x86_64",
"containerized": true,
"hostname": "docker-fleet-agent",
"id": "4ccba669f0df47fa3f57a9e4169ae7f1",
"ip": [
"172.18.0.4"
],
"mac": [
"02:42:ac:12:00:04"
],
"name": "docker-fleet-agent",
"os": {
"codename": "Core",
"family": "redhat",
"kernel": "5.11.0-44-generic",
"name": "CentOS Linux",
"platform": "centos",
"type": "linux",
"version": "7 (Core)"
}
},
"metricset": {
"name": "routes",
"period": 10000
},
"nats": {
"routes": {
"total": 1
},
"server": {
"id": "NAGYMNF4IADKFHPNJEJMQUWPYUVOWX3KC3V2UINL5QJYDVGIAZB7N3L6",
"time": "2022-01-12T02:52:26.015311657Z"
}
},
"service": {
"address": "http://elastic-package-service-nats-1:8222/routez",
"type": "nats"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
event.dataset | Event dataset | constant_keyword |
event.module | Event module | constant_keyword |
nats.routes.total | The number of registered routes | integer |
nats.server.id | The server ID | keyword |
nats.server.time | Server time of metric creation | date |
service.address | 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). | 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 . | keyword |
This is the subscriptions
dataset of the Nats package, in charge of retrieving
metrics about subscriptions from a Nats instance.
An example event for subscriptions
looks as following:
{
"@timestamp": "2022-01-12T02:57:55.837Z",
"agent": {
"ephemeral_id": "29d75d7c-e650-4bf4-ba7a-f769e4edd5da",
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"name": "docker-fleet-agent",
"type": "metricbeat",
"version": "8.0.0-beta1"
},
"data_stream": {
"dataset": "nats.subscriptions",
"namespace": "ep",
"type": "metrics"
},
"ecs": {
"version": "1.12.0"
},
"elastic_agent": {
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"snapshot": false,
"version": "8.0.0-beta1"
},
"event": {
"agent_id_status": "verified",
"dataset": "nats.subscriptions",
"duration": 11100010,
"ingested": "2022-01-12T02:57:59Z",
"module": "nats"
},
"host": {
"architecture": "x86_64",
"containerized": true,
"hostname": "docker-fleet-agent",
"id": "4ccba669f0df47fa3f57a9e4169ae7f1",
"ip": [
"172.18.0.4"
],
"mac": [
"02:42:ac:12:00:04"
],
"name": "docker-fleet-agent",
"os": {
"codename": "Core",
"family": "redhat",
"kernel": "5.11.0-44-generic",
"name": "CentOS Linux",
"platform": "centos",
"type": "linux",
"version": "7 (Core)"
}
},
"metricset": {
"name": "subscriptions",
"period": 10000
},
"nats": {
"subscriptions": {
"cache": {
"fanout": {
"avg": 0,
"max": 0
},
"hit_rate": 0,
"size": 1
},
"inserts": 0,
"matches": 1,
"removes": 0,
"total": 0
}
},
"service": {
"address": "http://elastic-package-service-nats-1:8222/subsz",
"type": "nats"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
event.dataset | Event dataset | constant_keyword |
event.module | Event module | constant_keyword |
nats.server.id | The server ID | keyword |
nats.server.time | Server time of metric creation | date |
nats.subscriptions.cache.fanout.avg | The average fanout served by cache | double |
nats.subscriptions.cache.fanout.max | The maximum fanout served by cache | integer |
nats.subscriptions.cache.hit_rate | The rate matches are being retrieved from cache | scaled_float |
nats.subscriptions.cache.size | The number of result sets in the cache | integer |
nats.subscriptions.inserts | The number of insert operations in subscriptions list | long |
nats.subscriptions.matches | The number of times a match is found for a subscription | long |
nats.subscriptions.removes | The number of remove operations in subscriptions list | long |
nats.subscriptions.total | The number of active subscriptions | integer |
service.address | 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). | 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 . | keyword |
This is the connection
dataset of the Nats package, in charge of retrieving detailed
metrics per connection from a Nats instance.
An example event for connection
looks as following:
{
"@timestamp": "2022-01-12T02:43:51.172Z",
"agent": {
"ephemeral_id": "3cf8068e-3998-4da7-b2f1-de14207c5d44",
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"name": "docker-fleet-agent",
"type": "metricbeat",
"version": "8.0.0-beta1"
},
"data_stream": {
"dataset": "nats.connection",
"namespace": "ep",
"type": "metrics"
},
"ecs": {
"version": "1.12.0"
},
"elastic_agent": {
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"snapshot": false,
"version": "8.0.0-beta1"
},
"event": {
"agent_id_status": "verified",
"dataset": "nats.connection",
"duration": 276175024,
"ingested": "2022-01-12T02:43:52Z",
"module": "nats"
},
"host": {
"architecture": "x86_64",
"containerized": true,
"hostname": "docker-fleet-agent",
"id": "4ccba669f0df47fa3f57a9e4169ae7f1",
"ip": [
"172.18.0.4"
],
"mac": [
"02:42:ac:12:00:04"
],
"name": "docker-fleet-agent",
"os": {
"codename": "Core",
"family": "redhat",
"kernel": "5.11.0-44-generic",
"name": "CentOS Linux",
"platform": "centos",
"type": "linux",
"version": "7 (Core)"
}
},
"metricset": {
"name": "connection",
"period": 10000
},
"nats": {
"connection": {
"idle_time": 0,
"in": {
"bytes": 10310992,
"messages": 644437
},
"name": "NATS Benchmark",
"out": {
"bytes": 0,
"messages": 0
},
"pending_bytes": 0,
"subscriptions": 0,
"uptime": 24
},
"server": {
"id": "NAMJNT4IYFE3N7FCYJWAKX3OKMQVIUSL7CN4EPBUXJNKSCTYCRHSVNTB"
}
},
"service": {
"address": "http://elastic-package-service-nats-1:8222/connz",
"type": "nats"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
event.dataset | Event dataset | constant_keyword |
event.module | Event module | constant_keyword |
nats.connection.idle_time | The period the connection is idle (sec) | long |
nats.connection.in.bytes | The amount of incoming bytes | long |
nats.connection.in.messages | The amount of incoming messages | long |
nats.connection.name | The name of the connection | keyword |
nats.connection.out.bytes | The amount of outgoing bytes | long |
nats.connection.out.messages | The amount of outgoing messages | long |
nats.connection.pending_bytes | The number of pending bytes of this connection | long |
nats.connection.subscriptions | The number of subscriptions in this connection | integer |
nats.connection.uptime | The period the connection is up (sec) | long |
nats.server.id | The server ID | keyword |
nats.server.time | Server time of metric creation | date |
service.address | 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). | 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 . | keyword |
This is the route
dataset of the Nats package, in charge of retrieving detailed
metric per route from a Nats instance.
An example event for route
looks as following:
{
"@timestamp": "2022-01-12T02:49:43.071Z",
"agent": {
"ephemeral_id": "7603b971-4c23-4474-94d7-736540cccfbc",
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"name": "docker-fleet-agent",
"type": "metricbeat",
"version": "8.0.0-beta1"
},
"data_stream": {
"dataset": "nats.route",
"namespace": "ep",
"type": "metrics"
},
"ecs": {
"version": "1.12.0"
},
"elastic_agent": {
"id": "9878d192-22ad-49b6-a6c2-9959b0815d04",
"snapshot": false,
"version": "8.0.0-beta1"
},
"event": {
"agent_id_status": "verified",
"dataset": "nats.route",
"duration": 37120483,
"ingested": "2022-01-12T02:49:47Z",
"module": "nats"
},
"host": {
"architecture": "x86_64",
"containerized": true,
"hostname": "docker-fleet-agent",
"id": "4ccba669f0df47fa3f57a9e4169ae7f1",
"ip": [
"172.18.0.4"
],
"mac": [
"02:42:ac:12:00:04"
],
"name": "docker-fleet-agent",
"os": {
"codename": "Core",
"family": "redhat",
"kernel": "5.11.0-44-generic",
"name": "CentOS Linux",
"platform": "centos",
"type": "linux",
"version": "7 (Core)"
}
},
"metricset": {
"name": "route",
"period": 10000
},
"nats": {
"route": {
"in": {
"bytes": 0,
"messages": 0
},
"ip": "172.23.0.2",
"out": {
"bytes": 0,
"messages": 0
},
"pending_size": 0,
"port": 43132,
"remote_id": "ND6TIOITFXLQL7IOQ6YF4YA76FO5DZKZ7RADTQFJH5Y22554RBAN23HE",
"subscriptions": 0
},
"server": {
"id": "NDLSAJ5QGWF5IZJSOSOC7P22NTXGFIQMULUEZR2VC4HT4STJU6L36AIB"
}
},
"service": {
"address": "http://elastic-package-service-nats-1:8222/routez",
"type": "nats"
}
}
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_keyword |
ecs.version | ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events. | keyword |
event.dataset | Event dataset | constant_keyword |
event.module | Event module | constant_keyword |
nats.route.in.bytes | The amount of incoming bytes | long |
nats.route.in.messages | The amount of incoming messages | long |
nats.route.ip | The ip of the route | ip |
nats.route.out.bytes | The amount of outgoing bytes | long |
nats.route.out.messages | The amount of outgoing messages | long |
nats.route.pending_size | The number of pending routes | long |
nats.route.port | The port of the route | integer |
nats.route.remote_id | The remote id on which the route is connected to | keyword |
nats.route.subscriptions | The number of subscriptions in this connection | integer |
nats.server.id | The server ID | keyword |
nats.server.time | Server time of metric creation | date |
service.address | 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). | 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 . | keyword |
Version | Details |
---|---|
1.3.1 | Enhancement View pull request Added categories and/or subcategories. |
1.3.0 | Enhancement View pull request Update to ECS 8.0 |
1.2.1 | Bug fix View pull request Change test public IPs to the supported subset |
1.2.0 | Enhancement View pull request Release nats package for v8.0.0 |
1.1.2 | Enhancement View pull request Uniform with guidelines |
1.1.1 | Bug fix View pull request Fix logic that checks for the 'forwarded' tag |
1.1.0 | Enhancement View pull request Update to ECS 1.12.0 |
1.0.0 | Enhancement View pull request Release NATS as GA |
0.5.3 | Enhancement View pull request Convert to generated ECS fields |
0.5.2 | Enhancement View pull request update to ECS 1.11.0 |
0.5.1 | Enhancement View pull request Escape special characters in docs |
0.5.0 | Enhancement View pull request Update integration description |
0.4.0 | Enhancement View pull request Set "event.module" and "event.dataset" |
0.3.0 | Enhancement View pull request update to ECS 1.10.0 and add event.original options |
0.2.0 | Bug fix View pull request Fix stack compatability |
0.1.4 | Bug fix View pull request Fix filters on dashboards |
0.1.3 | Enhancement View pull request Updating package owner Enhancement View pull request update to ECS 1.9.0 |
0.1.2 | Bug fix View pull request Correct sample event file. |
0.1.1 | Bug fix View pull request Change kibana.version constraint to be more conservative. |
0.1.0 | Enhancement View pull request initial release |