You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare OTel Elasticsearch exporter with the credentials of the output (#5469)
When an OTel exporter is found in the configuration, and it is an Elasticsearch
exporter, it looks for a prepared output with the same name, and copies its
credentials.
# - breaking-change: a change to previously-documented behavior
3
+
# - deprecation: functionality that is being removed in a later release
4
+
# - bug-fix: fixes a problem in a previous version
5
+
# - enhancement: extends functionality but does not break or fix existing behavior
6
+
# - feature: new functionality
7
+
# - known-issue: problems that we are aware of in a given version
8
+
# - security: impacts on the security of a product or a user’s deployment.
9
+
# - upgrade: important information for someone upgrading from a prior version
10
+
# - other: does not fit into any of the other categories
11
+
kind: enhancement
12
+
13
+
# Change summary; a 80ish characters long description of the change.
14
+
summary: Add credentials to OTel Elasticsearch exporters
15
+
16
+
# Long description; in case the summary is not enough to describe the change
17
+
# this field accommodate a description without length limits.
18
+
# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment.
19
+
description: When a policy includes OTel configuration with Elasticsearch exporters, it configures their credentials using the credentials in the Elasticsearch output.
20
+
21
+
# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc.
22
+
component: fleet-server
23
+
24
+
# PR URL; optional; the PR number that added the changeset.
25
+
# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added.
26
+
# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number.
27
+
# Please provide it if you are adding a fragment for a different PR.
0 commit comments