Skip to content

Commit

Permalink
package/kibana - define span.id field (#11895)
Browse files Browse the repository at this point in the history
The kibana.audit data stream was missing a mapping
for the span.id field.

Fixes #11658
Fixes #11130
Fixes #10691
Fixes #10514
Fixes #9839
  • Loading branch information
andrewkroh authored Dec 10, 2024
1 parent dfe265e commit b5f8aa2
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 1 deletion.
5 changes: 5 additions & 0 deletions packages/kibana/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "2.5.5"
changes:
- description: Add field mapping for the ECS `span.id` field.
type: bugfix
link: https://github.com/elastic/integrations/pull/11895
- version: "2.5.4"
changes:
- description: Adding missing fields in the Kibana status metricset
Expand Down
2 changes: 2 additions & 0 deletions packages/kibana/data_stream/audit/fields/ecs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -52,3 +52,5 @@
external: ecs
- name: client.ip
external: ecs
- name: span.id
external: ecs
1 change: 1 addition & 0 deletions packages/kibana/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ UI in Kibana.
| process.pid | Process id. | long |
| related.user | All the user names or other user identifiers seen on the event. | keyword |
| service.node.roles | Roles 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` or both. In the case of Elasticsearch, the `service.node.role` could be `master` or `data` or both. Other services could use this to distinguish between a `web` and `worker` role running as part of the service. | keyword |
| span.id | Unique identifier of the span within the scope of its trace. A span represents an operation within a transaction, such as a request to another service, or a database query. | keyword |
| trace.id | Unique identifier of the trace. A trace groups multiple events like transactions that belong together. For example, a user request handled by multiple inter-connected services. | keyword |
| transaction.id | Unique identifier of the transaction within the scope of its trace. A transaction is the highest level of work measured within a service, such as a request to a server. | keyword |
| url.domain | Domain of the url, such as "www.elastic.co". In some cases a URL may refer to an IP and/or port directly, without a domain name. In this case, the IP address would go to the `domain` field. If the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC 2732), the `[` and `]` characters should also be captured in the `domain` field. | keyword |
Expand Down
2 changes: 1 addition & 1 deletion packages/kibana/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: kibana
title: Kibana
version: 2.5.4
version: 2.5.5
description: Collect logs and metrics from Kibana with Elastic Agent.
type: integration
icons:
Expand Down

0 comments on commit b5f8aa2

Please sign in to comment.