From e914547a8da8affca0246b32804f9eedb9f3617e Mon Sep 17 00:00:00 2001 From: Aleksandr Maus Date: Sat, 13 Jul 2024 19:12:28 -0400 Subject: [PATCH] Add changelog --- .../feature_elasticsearch_otel_model.yaml | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 .chloggen/feature_elasticsearch_otel_model.yaml diff --git a/.chloggen/feature_elasticsearch_otel_model.yaml b/.chloggen/feature_elasticsearch_otel_model.yaml new file mode 100644 index 0000000000000..1f44b5faa5135 --- /dev/null +++ b/.chloggen/feature_elasticsearch_otel_model.yaml @@ -0,0 +1,27 @@ +# Use this changelog template to create an entry for release notes. + +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' +change_type: enhancement + +# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) +component: elasticsearchexporter + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: Introduce an experimental OTel native mode serialization + +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. +issues: [] + +# (Optional) One or more lines of additional information to render under the primary note. +# These lines will be padded with 2 spaces and then inserted directly into the document. +# Use pipe (|) for multiline entries. +subtext: + +# If your change doesn't affect end users or the exported elements of any package, +# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. +# Optional: The change log or logs in which this entry should be included. +# e.g. '[user]' or '[user, api]' +# Include 'user' if the change is relevant to end users. +# Include 'api' if there is a change to a library API. +# Default: '[user]' +change_logs: []