Merge main

Author: antonjim-te

.chloggen/TEMPLATE.yaml

@@ -1,3 +1,5 @@
+# Use this changelog template to create an entry for release notes.
+
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
 change_type:
 
@@ -14,3 +16,10 @@ issues: []
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext:
+
+# 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: []

.chloggen/codeboten_add-periodic-internal-timeout.yaml renamed to .chloggen/add-exemplars-logging.yaml

@@ -2,13 +2,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: service
+component: loggingexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Add support for `interval` and `timeout` configuration in periodic reader"
+note: Adds exemplars logging to the logging exporter when `detailed` verbosity level is set.
 
 # One or more tracking issues or pull requests related to the change
-issues: [7641]
+issues: [7912]
 
 # (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.

.chloggen/codeboten_add-console-exporter.yaml

@@ -0,0 +1,24 @@
+# The directory that stores individual changelog entries.
+# Each entry is stored in a dedicated yaml file.
+# - 'chloggen new' will copy the 'template_yaml' to this directory as a new entry file.
+# - 'chloggen validate' will validate that all entry files are valid.
+# - 'chloggen update' will read and delete all entry files in this directory, and update 'changelog_md'.
+# Specify as relative path from root of repo.
+# (Optional) Default: .chloggen
+entries_dir: .chloggen
+
+# This file is used as the input for individual changelog entries.
+# Specify as relative path from root of repo.
+# (Optional) Default: .chloggen/TEMPLATE.yaml
+template_yaml: .chloggen/TEMPLATE.yaml
+
+# The CHANGELOG file or files to which 'chloggen update' will write new entries
+# (Optional) Default filename: CHANGELOG.md
+change_logs:
+  user: CHANGELOG.md
+  api: CHANGELOG-API.md
+
+# The default change_log or change_logs to which an entry should be added.
+# If 'change_logs' is specified in this file, and no value is specified for 'default_change_logs',
+# then 'change_logs' MUST be specified in every entry file.
+default_change_logs: [user]

.chloggen/codeboten_add-tracer-provider.yaml

@@ -0,0 +1,12 @@
+# 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. otlpreceiver)
+component: exporter/exporterhelper
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Introduce a new exporter helper that operates over client-provided requests instead of pdata
+
+# One or more tracking issues or pull requests related to the change
+issues: [7874]
+

.chloggen/codeboten_jul7-otlp.yaml

@@ -1,16 +1,25 @@
+# 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. otlpreceiver)
 component: otlpreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add http url paths per signal config options to otlpreceiver 
+note: Export HTTPConfig as part of the API for creating the otlpreceiver configuration.
 
 # One or more tracking issues or pull requests related to the change
-issues: [7511]
+issues: [8175]
 
 # (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:
+subtext: Changes signature of receiver/otlpreceiver/config.go type httpServerSettings to HTTPConfig.
+
+# 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: [api]

.chloggen/codeboten_may-29-otlp-export.yaml

@@ -1,16 +1,25 @@
+# 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. otlpreceiver)
-component: scraperhelper
+component: configgrpc
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Adding optional timeout field to scrapers
+note: "Add support for :authority pseudo-header in grpc client"
 
 # One or more tracking issues or pull requests related to the change
-issues: [7951]
+issues: [8228]
 
 # (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:
+
+# 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: []

.chloggen/codeboten_update-jsonschema-0001b0391785d880ce052f4c6fd85c5a4e0474fa.yaml

@@ -1,6 +1,6 @@
 # This GitHub action is used to compare API state snapshots of Main
-# to Head of the PR in order to validate releases are not breaking 
-# backwards compatibility. 
+# to Head of the PR in order to validate releases are not breaking
+# backwards compatibility.
 #
 # This GitHub action will fail if there are incompatible changes.
 #
@@ -15,44 +15,47 @@ on:
 jobs:
   Check-Compatibility:
     runs-on: macos-latest
+    env:
+      BASE_REF: ${{ github.base_ref }}
+      HEAD_REF: ${{ github.head_ref }}
     steps:
 
       - name: Checkout-Main
         uses: actions/checkout@v3
-        with: 
+        with:
           ref: ${{ github.base_ref }}
           path: ${{ github.base_ref }}
 
       - name: Checkout-HEAD
-        uses: actions/checkout@v3 
-        with: 
+        uses: actions/checkout@v3
+        with:
           path: ${{ github.head_ref }}
 
       - name: Setup Go
         uses: actions/setup-go@v4
         with:
-          go-version: ~1.19.11
-      
+          go-version: ~1.20.7
+
       # Generate apidiff states of Main
       - name: Generate-States
         run: |
-          cd ${{ github.base_ref }}
+          cd $BASE_REF
           make apidiff-build
-          
+
       # Compare apidiff states of Main with PR
       - name: Compare-States
-        env: 
+        env:
           CI: true
           COMPARE_OPTS: -d "../${{ github.base_ref }}/internal/data/apidiff"
         run: |
-          cd ${{ github.head_ref }}
+          cd $HEAD_REF
           make apidiff-compare
-      
+
       # Fail GitHub Action if there are incompatible changes
       - name: Check-States
-        env: 
+        env:
           CI: true
           COMPARE_OPTS: -d "../${{ github.base_ref }}/internal/data/apidiff" -c
         run: |
-          cd ${{ github.head_ref }}
+          cd $HEAD_REF
           make apidiff-compare

.chloggen/config.yaml

@@ -19,7 +19,7 @@ jobs:
       - name: Setup Go
         uses: actions/setup-go@v4
         with:
-          go-version: ~1.19.11
+          go-version: ~1.20.7
       - name: Cache Go
         uses: actions/cache@v3
         env: