OpenTelemetry instrumentation for splunk by Dartastic.io. Adds standard OpenTelemetry observability to applications that use splunk. Changelog excerpt: ### Added - First open-source release on pub.dev. Depends on `dartastic_opentelemetry_api >=1.0.0-rc.4 <1.0.0-rc.5`only; the application chooses and initializes the OpenTelemetry SDK.

In case you missed it: OpenTelemetry (OTel) has officially achieved CNCF graduated status! It now stands proudly alongside amazing open source projects such as Kubernetes and Prometheus, to name just a few. It’s been a long journey, and we’re very...

Discover how to eliminate OpenTelemetry memory bottlenecks by replacing point-to-point collector connections with an Event-Driven Architecture (EDA) design.

Claude Code の利用状況を把握する方法を、公式ドキュメントに沿って整理します。プラン別のアナリティクスダッシュボードと、OpenTelemetry の設定、管理者設定で配る際の注意点をまとめました。

Kubernetes Native OTel Collector Management at Scale

Every system has work that runs on a schedule. Wolverine turns a cron job into an ordinary message, so it gets the outbox, retries, dead letters, OpenTelemetry tracing and once-per-cluster execution f...

Explore Oracle AI Database observability with Spring Boot, OpenTelemetry, and Grafana. Connect traces, application logs, and database metrics.

We're giving teams a way to run native OTLP pipelines in Grafana Cloud without giving up the power and flexibility Alloy is known for.

Amazon CloudWatch now supports bearer token authentication, using API keys (bearer tokens), as an additional option for sending OpenTelemetry traces to the AWS X-Ray OpenTelemetry Protocol (OTLP) traces endpoint. Any OTLP/HTTP client that can set an Authorization header, including the OpenTelemetry Collector and OpenTelemetry SDK exporters, can now authenticate with a bearer token instead of signing requests with AWS Signature Version 4 (SigV4). This helps teams send traces from workloads that can't use the AWS SDK or short-term credentials, such as applications running on premises or in other clouds, CI/CD pipelines, and third-party tools that support only a static Authorization header. SigV4 remains the recommended authentication method for sending traces to CloudWatch, and the AWS Distro for OpenTelemetry (ADOT) SDKs continue to use SigV4 by default with no changes required. Traces sent with either method get the same CloudWatch capabilities, including Transaction Search, Amazon CloudWatch Application Signals, and Amazon CloudWatch Omni. Bearer token authentication for traces is available in all commercial AWS Regions where the AWS X-Ray OTLP traces endpoint is available. To learn more, see Setting up bearer token authentication for traces in the AWS X-Ray Developer Guide.

Amazon CloudWatch now supports bearer token authentication, using API keys (bearer tokens), as an additional option for sending OpenTelemetry traces to the AWS X-Ray OpenTelemetry Protocol (OTLP) traces endpoint. Any OTLP/HTTP client that can set an Authorization header, including the OpenTelemetry Collector and OpenTelemetry SDK exporters, can now authenticate with a bearer token instead of signing requests with AWS Signature Version 4 (SigV4). This helps teams send traces from workloads that can't use the AWS SDK or short-term credentials, such as applications running on premises or in other clouds, CI/CD pipelines, and third-party tools that support only a static Authorization header. SigV4 remains the recommended authentication method for sending traces to CloudWatch, and the AWS Distro for OpenTelemetry (ADOT) SDKs continue to use SigV4 by default with no changes required. Traces sent with either method get the same CloudWatch capabilities, including Transaction Search, Amazon CloudWatch Application Signals, and Amazon CloudWatch Omni. Bearer token authentication for traces is available in all commercial AWS Regions where the AWS X-Ray OTLP traces endpoint is available. To learn more, see Setting up bearer token authentication for traces in the AWS X-Ray Developer Guide.

https://aws.amazon.com/cloudwatch/ now supports bearer token authentication, using API keys (bearer tokens), as an additional option for sending OpenTelemetry traces to the AWS X-Ray OpenTelemetry Protocol (OTLP) traces endpoint. Any OTLP/HTTP client that can set an Authorization header, including the OpenTelemetry Collector and OpenTelemetry SDK exporters, can now authenticate with a bearer token instead of signing requests with AWS Signature Version 4 (SigV4). This helps teams send traces from workloads that can't use the AWS SDK or short-term credentials, such as applications running on premises or in other clouds, CI/CD pipelines, and third-party tools that support only a static Authorization header. SigV4 remains the recommended authentication method for sending traces to CloudWatch, and the AWS Distro for OpenTelemetry (ADOT) SDKs continue to use SigV4 by default with no changes required. Traces sent with either method get the same CloudWatch capabilities, including Transaction Search, Amazon CloudWatch Application Signals, and Amazon CloudWatch Omni. Bearer token authentication for traces is available in all commercial AWS Regions where the AWS X-Ray OTLP traces endpoint is available. To learn more, see https://docs.aws.amazon.com/xray/latest/devguide/xray-opentelemetry-bearer-token.html in the AWS X-Ray Developer Guide.

Amazon CloudWatch now supports API key bearer token authentication for sending OpenTelemetry traces to AWS X-Ray OTLP endpoint, enabling traces from on-premises and third-party tools.