add baseURL config

Author: ArturSantosTD

.chloggen/azureblobexporter-alpha.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: azureblobexporter
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: change to alpha for azure blob exporter
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [39272]
+
+# (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: [user]

.chloggen/elasticsearchexporter_telemetry-log-failed-docs-source.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: Add `telemetry::log_failed_docs_input` and `telemetry::log_failed_docs_input_rate_limit` config to facilitate debugging of failed bulk request items
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [39205]
+
+# (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: Additionally, log a warning about potentially exposing sensitive data on any enabled `telemetry` config.
+
+# 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: [user]

.chloggen/kafkareceiver-persignal-config.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: deprecation
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: kafkareceiver
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add signal-specific topic and encoding config, deprecate existing topic/encoding config.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [32735]
+
+# (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: [user]

.chloggen/operator-resource-attributes.yaml

@@ -0,0 +1,15 @@
+change_type: enhancement
+
+component: k8sattributesprocessor
+
+note: Add option to configure automatic resource attributes - with annotation prefix
+
+issues: [37114]
+
+subtext: |
+  Implements [Specify resource attributes using Kubernetes annotations](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/k8s-attributes.md#specify-resource-attributes-using-kubernetes-annotations).
+  
+  If you are using the file log receiver, you can now create the same resource attributes as traces (via OTLP) received
+  from an application instrumented with the OpenTelemetry Operator -
+  simply by adding the `extract: { otel_annotations: true }` configuration to the `k8sattributesprocessor` processor.
+  See the [documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/k8sattributesprocessor/README.md#config-example) for more details.

.chloggen/optional-signaltometrics.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: signaltometricsconnector
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Allow to configure `optional` attributes which are copied as-is to the output metric.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [38600]
+
+# (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: [user]

.chloggen/splunk_enterprise_receiver_metric_fix.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: bug_fix
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: splunkenterprisereceiver
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Fixes `otelcol_scraper_errored_metric_points` metric, which was not incrementing properly
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [38691]
+
+# (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: []

cmd/opampsupervisor/supervisor/supervisor_test.go

@@ -6,6 +6,7 @@ package supervisor
 import (
 	"bytes"
 	"context"
+	"errors"
 	"fmt"
 	"net"
 	"os"
@@ -598,7 +599,7 @@ service:
 					},
 					rcs,
 				)
-				return fmt.Errorf("unexpected error")
+				return errors.New("unexpected error")
 			},
 			updateEffectiveConfigFunc: func(_ context.Context) error {
 				return nil
@@ -853,7 +854,7 @@ func Test_handleAgentOpAMPMessage(t *testing.T) {
 		mc := &mockOpAMPClient{
 			updateEffectiveConfigFunc: func(_ context.Context) error {
 				updatedClientEffectiveConfig = true
-				return fmt.Errorf("unexpected error")
+				return errors.New("unexpected error")
 			},
 		}
 

cmd/telemetrygen/internal/common/config.go

@@ -4,7 +4,7 @@
 package common
 
 import (
-	"fmt"
+	"errors"
 	"strconv"
 	"strings"
 	"time"
@@ -15,8 +15,8 @@ import (
 )
 
 var (
-	errFormatOTLPAttributes       = fmt.Errorf("value should be in one of the following formats: key=\"value\", key=true, key=false, or key=<integer>")
-	errDoubleQuotesOTLPAttributes = fmt.Errorf("value should be a string wrapped in double quotes")
+	errFormatOTLPAttributes       = errors.New("value should be in one of the following formats: key=\"value\", key=true, key=false, or key=<integer>")
+	errDoubleQuotesOTLPAttributes = errors.New("value should be a string wrapped in double quotes")
 )
 
 const (

cmd/telemetrygen/internal/common/validate.go

@@ -5,14 +5,14 @@ package common
 
 import (
 	"encoding/hex"
-	"fmt"
+	"errors"
 )
 
 var (
-	errInvalidTraceIDLength = fmt.Errorf("TraceID must be a 32 character hex string, like: 'ae87dadd90e9935a4bc9660628efd569'")
-	errInvalidSpanIDLength  = fmt.Errorf("SpanID must be a 16 character hex string, like: '5828fa4960140870'")
-	errInvalidTraceID       = fmt.Errorf("failed to create traceID byte array from the given traceID, make sure the traceID is a hex representation of a [16]byte, like: 'ae87dadd90e9935a4bc9660628efd569'")
-	errInvalidSpanID        = fmt.Errorf("failed to create SpanID byte array from the given SpanID, make sure the SpanID is a hex representation of a [8]byte, like: '5828fa4960140870'")
+	errInvalidTraceIDLength = errors.New("TraceID must be a 32 character hex string, like: 'ae87dadd90e9935a4bc9660628efd569'")
+	errInvalidSpanIDLength  = errors.New("SpanID must be a 16 character hex string, like: '5828fa4960140870'")
+	errInvalidTraceID       = errors.New("failed to create traceID byte array from the given traceID, make sure the traceID is a hex representation of a [16]byte, like: 'ae87dadd90e9935a4bc9660628efd569'")
+	errInvalidSpanID        = errors.New("failed to create SpanID byte array from the given SpanID, make sure the SpanID is a hex representation of a [8]byte, like: '5828fa4960140870'")
 )
 
 func ValidateTraceID(traceID string) error {

cmd/telemetrygen/pkg/logs/config.go

@@ -4,7 +4,7 @@
 package logs
 
 import (
-	"fmt"
+	"errors"
 
 	"github.com/spf13/pflag"
 
@@ -59,7 +59,7 @@ func (c *Config) SetDefaults() {
 // Validate validates the test scenario parameters.
 func (c *Config) Validate() error {
 	if c.TotalDuration <= 0 && c.NumLogs <= 0 {
-		return fmt.Errorf("either `logs` or `duration` must be greater than 0")
+		return errors.New("either `logs` or `duration` must be greater than 0")
 	}
 
 	if c.TraceID != "" {

cmd/telemetrygen/pkg/logs/logs.go

@@ -5,6 +5,7 @@ package logs
 
 import (
 	"context"
+	"errors"
 	"fmt"
 	"sync"
 	"sync/atomic"
@@ -147,7 +148,7 @@ func createExporter(cfg *Config, logger *zap.Logger) (sdklog.Exporter, error) {
 func parseSeverity(severityText string, severityNumber int32) (string, log.Severity, error) {
 	sn := log.Severity(severityNumber)
 	if sn < log.SeverityTrace1 || sn > log.SeverityFatal4 {
-		return "", log.SeverityUndefined, fmt.Errorf("severity-number is out of range, the valid range is [1,24]")
+		return "", log.SeverityUndefined, errors.New("severity-number is out of range, the valid range is [1,24]")
 	}
 
 	// severity number should match well-known severityText

cmd/telemetrygen/pkg/metrics/aggregation_temporality.go

@@ -4,7 +4,7 @@
 package metrics
 
 import (
-	"fmt"
+	"errors"
 
 	"go.opentelemetry.io/otel/sdk/metric/metricdata"
 )
@@ -20,7 +20,7 @@ func (t *AggregationTemporality) Set(v string) error {
 		*t = AggregationTemporality(metricdata.CumulativeTemporality)
 		return nil
 	default:
-		return fmt.Errorf(`temporality must be one of "delta" or "cumulative"`)
+		return errors.New(`temporality must be one of "delta" or "cumulative"`)
 	}
 }
 

cmd/telemetrygen/pkg/metrics/config.go

@@ -4,7 +4,7 @@
 package metrics
 
 import (
-	"fmt"
+	"errors"
 
 	"github.com/spf13/pflag"
 	"go.opentelemetry.io/otel/sdk/metric/metricdata"
@@ -66,7 +66,7 @@ func (c *Config) SetDefaults() {
 // Validate validates the test scenario parameters.
 func (c *Config) Validate() error {
 	if c.TotalDuration <= 0 && c.NumMetrics <= 0 {
-		return fmt.Errorf("either `metrics` or `duration` must be greater than 0")
+		return errors.New("either `metrics` or `duration` must be greater than 0")
 	}
 
 	if c.TraceID != "" {

cmd/telemetrygen/pkg/traces/config.go

@@ -4,7 +4,7 @@
 package traces
 
 import (
-	"fmt"
+	"errors"
 	"time"
 
 	"github.com/spf13/pflag"
@@ -64,7 +64,7 @@ func (c *Config) SetDefaults() {
 // Validate validates the test scenario parameters.
 func (c *Config) Validate() error {
 	if c.TotalDuration <= 0 && c.NumTraces <= 0 {
-		return fmt.Errorf("either `traces` or `duration` must be greater than 0")
+		return errors.New("either `traces` or `duration` must be greater than 0")
 	}
 	return nil
 }

connector/signaltometricsconnector/README.md

@@ -146,12 +146,38 @@ attributes:
   - key: datapoint.foo
   - key: datapoint.bar
     default_value: bar
+  - key: datapoint.baz
+    optional: true
 ```
 
 If attributes are specified then a separate metric will be generated for each unique
-set of attribute values. Optionally, a `default_value` can be used to always include
-the attribute with the value of the attribute defaulting to the value specified in
-`default_value` if the incoming data is missing that attribute.
+set of attribute values. There are three behaviors that can be configured for an
+attribute:
+
+- Without any extra parameters: `datapoint.foo` in the above yaml is an example
+  of such configuration. In this configuration, only the signals which have the said
+  attribute are processed with the attribute's value as one of the attributes for
+  the output metric. If the attribute is missing then the signal is not processed.
+- With `default_value`: `datapoint.bar` in the above yaml is an example of such
+  configuration. In this configuration all the signals are processed irrespective
+  of the attribute being present or not in the input signal. The output metric
+  is categorized as per the incoming value of the attribute and an extra bucket
+  exists with the attribute set to the configured default value for all the signals
+  that were missing the configured attribute.
+- With `optional` set to `true`: `datapoint.baz` in the above yaml is an example
+  of such configuration. If the attribute is configured with `optional` and present
+  in the incoming signal then it will be added directly to the output metric. If
+  it is absent then a new metric with missing attributes will be created. In addition,
+  the `optional` attribute will not impact the decision i.e. even if the `optional`
+  attributes are not present in the incoming signal, the signal will be processed
+  and will produce a metric given all other non-optional attributes are present
+  or have a default value defined.
+
+Note that resource attributes are handled differently, check the resource attributes
+section for more details on this. Think of `attributes` as conditional filters for
+choosing which attributes should be included in the output metric whereas
+`include_resource_attributes` is an include list for customizing resource attributes
+of the output metric.
 
 ### Conditions
 
@@ -201,16 +227,23 @@ include_resource_attributes:
   - key: resource.foo # Include resource.foo attribute if present
   - key: resource.bar # Always include resource.bar attribute, default to bar
     default_value: bar
+  - key: resource.baz # Optional resource.baz attribute is added if present
+    optional: true
 ```
 
-With the above configuration the produced metrics would only have the couple of
-resource attributes specified in the list:
+With the above configuration the produced metrics would have the following
+resource attributes:
 
 - `resource.foo` will be present for the produced metrics if the incoming data also
-  has the attribute defined.
+  has the attribute defined. If the attribute is missing in the incoming data the
+  output metric will be produced without the said attribute.
 - `resource.bar` will always be present because of the `default_value`. If the incoming
   data does not have a resource attribute with name `resource.bar` then the configured
   `default_value` of `bar` will be used.
+- `resource.baz` will behave exactly same as `resource.foo`. Since resource attributes
+  are basically an include list, the `optional` option is a no-op i.e. the resource
+  attributes with `optional` set to `true` behaves identical to an attribute configured
+  without `default_value` or `optional`.
 
 ### Single writer
 

connector/signaltometricsconnector/config/config.go

@@ -123,6 +123,7 @@ func (c *Config) Unmarshal(collectorCfg *confmap.Conf) error {
 
 type Attribute struct {
 	Key          string `mapstructure:"key"`
+	Optional     bool   `mapstructure:"optional"`
 	DefaultValue any    `mapstructure:"default_value"`
 }
 
@@ -185,6 +186,9 @@ func (mi *MetricInfo) validateAttributes() error {
 		if attr.Key == "" {
 			return fmt.Errorf("attribute key missing")
 		}
+		if attr.DefaultValue != nil && attr.Optional {
+			return errors.New("only one of default_value or optional should be set")
+		}
 		if _, ok := duplicate[attr.Key]; ok {
 			return fmt.Errorf("duplicate key found in attributes config: %s", attr.Key)
 		}