Journald Receiver Detected Status Issue

Oct 13, 2025 by recoveryshake.com 37 views

Weekly Report: 2025-03-04 - 2025-03-11

This report provides an overview of the issues, components, and other relevant information for the OpenTelemetry Collector Contrib project from March 4th to March 11th.

Issues Report

There are 52 new issues reported in the past week, including:

tailsamplingprocessor: Decision Timer Latency Metric is misleading (#38502)
Journald Receiver Detected Status Issue (#38498)
Webhook Exporter for OpenTelemetry: Push Data to HTTP Endpoint (#38496)
Support raw_json Encoding for Kafka Exporter (Azure Event Hub Compatibility) (#38495)
Enhancement of SignalToMetricsConnector: Key Name Override & Null Value Handling (#38494)
The function of disabling metrics does not work (#38489)
build-example failing due to supposedly missing go.sum entries (#38488)
Azure Event Hub receiver empty offset not starting at latest (#38487)
Using custom schema for metrics (#38485)
Enable Partitioning by Specific Attribute for Logs & Metrics (#38484)
No make commands work properly (using a Mac) (#38481)
migrate to AWS v2 SDK (#38479)
Resolve the logs/traces sampling priority discrepancy in probabilistic sampler processor (#38469)
LogRecordToEnvelope does not handle exceptions (#38432)
Add support for Alertmanager api v2 (#38417)
Consolidate common Kafka configuration within internal/kafka (#38411)
rpc error: code = InvalidArgument desc = One or more TimeSeries could not be written (#38405)
Add ability to handle Split metrics (#38402)
Allow fetching CloudWatch log groups filtered using a given account ID (#38391)
Multiple apache/arrow versions (#38387)
support setting metric type in carbon receiver plaintext (#38373)
Not able to receive metrics from logs count connector (#38304)
Docker receiver doesn't show stats for all containers (#38265)
Incorrect "span_metrics_calls_total" Metric Value for SpanMetrics when Otel-Collector is Restarted (#38262)
File compression missmatch for exporter and reciver (#38250)
Failing to fetch index stats metrics (#38188)
Label Dropping Issue in OTel Prometheus Receiver for aerospike_vector_search_requests (#38172)
Changed behaviour of resource generation in Prometheus receiver since upgrade to Prometheus 3.X (#38097)
Support Oauth 2.0 Token Exchange In oauth2clientauth (#38086)
Alertmanager exporter should allow additional labels (#38063)
Add e2e test cases for "archive" feature (#38056)
Add support for failover statements (#38051)
OpenSearch exporter failed to export data (#38048)
cri-o pod logs incompatibility with filelog receiver (#38002)
Failing integration test: No such image: nginx:1.17 (#37933)
Error when using passthrough_logs=true option (#37888)
please redact the exporter sumologic url (#37859)
docker_stats issue with docker.sock permissions (#37849)
Extend Kafka exporter to support profiling signal (#37837)
Add ability to customize permissions of socket when using UDS server (#37807)
oidcauthextension - do not verify issuer and issue_url match (follow up) (#37794)
metricstransform processor not working as expected - sum of 2 summary prometheus metrics is not created with only the configured label_set (#37792)
oidcauthextension - do not verify issuer and issuer_url match (#37780)
change database_name_attribute to accept a list of values (#37777)
Incorrect/misleading Documentation for receiver/kafkametrics TLS Configuration (#37776)
Internal telemetry metrics records fail to update (#37771)
Variable sampling frequency for interval processor (#37744)
Exporter not handling span links correctly (#37724)
dockerstats/different containers runtimes (#37710)
Contains one element in array (#37704)
add a feature to the metricstransformprocessor to allow custom code to do the transformation (#37699)
Add ability to add element in array (#37672)

There are 52 issues needing triage, including:

tailsamplingprocessor: Decision Timer Latency Metric is misleading (#38502)
Journald Receiver Detected Status Issue (#38498) *
Q&A: OpenTelemetry Collector Contrib

Q: What is the OpenTelemetry Collector Contrib project?

A: The OpenTelemetry Collector Contrib project is a collection of open-source components that can be used to collect and process telemetry data from various sources. It is a part of the OpenTelemetry project, which aims to provide a standard way of collecting and processing telemetry data.

Q: What are the main components of the OpenTelemetry Collector Contrib project?

A: The main components of the OpenTelemetry Collector Contrib project include:

Receivers: These are components that collect telemetry data from various sources, such as logs, metrics, and traces.
Processors: These are components that process the collected telemetry data, such as filtering, aggregating, and transforming it.
Exporters: These are components that export the processed telemetry data to various destinations, such as databases, message queues, and cloud services.

Q: What are the benefits of using the OpenTelemetry Collector Contrib project?

A: The benefits of using the OpenTelemetry Collector Contrib project include:

Standardization: The OpenTelemetry project provides a standard way of collecting and processing telemetry data, which makes it easier to integrate with other tools and systems.
Flexibility: The OpenTelemetry Collector Contrib project provides a wide range of components that can be used to collect and process telemetry data from various sources.
Scalability: The OpenTelemetry Collector Contrib project is designed to handle large volumes of telemetry data and can be scaled up or down as needed.

Q: How do I get started with the OpenTelemetry Collector Contrib project?

A: To get started with the OpenTelemetry Collector Contrib project, you can:

Read the documentation: The OpenTelemetry project provides extensive documentation on how to use the Collector Contrib project.
Join the community: The OpenTelemetry project has an active community of developers and users who can provide support and guidance.
Try out the examples: The OpenTelemetry project provides examples of how to use the Collector Contrib project in various scenarios.

Q: What are some common use cases for the OpenTelemetry Collector Contrib project?

A: Some common use cases for the OpenTelemetry Collector Contrib project include:

Monitoring and logging: The OpenTelemetry Collector Contrib project can be used to collect and process logs and metrics from various sources.
Tracing and debugging: The OpenTelemetry Collector Contrib project can be used to collect and process traces and debug information from various sources.
Analytics and reporting: The OpenTelemetry Collector Contrib project can be used to collect and process telemetry data for analytics and reporting purposes.

Q: How do I contribute to the OpenTelemetry Collector Contrib project?

A: To contribute to the OpenTelemetry Collector Contrib project, you can:

Submit a pull request: You can submit a pull request to the OpenTelemetry project with your changes.
Join the community: You can join the OpenTelemetry community and participate in discussions and decision-making processes.
Report issues: You can report issues and bugs to the OpenTelemetry project.

Q: What are some best practices for using the OpenTelemetry Collector Contrib project?

A: Some best practices for using the OpenTelemetry Collector Contrib project include:

Use the standard configuration: Use the standard configuration for the Collector Contrib project to ensure that it is properly configured.
Monitor and log: Monitor and log the Collector Contrib project to ensure that it is working correctly.
Test and validate: Test and validate the Collector Contrib project to ensure that it is working correctly in various scenarios.