-
This prints constantly from the collector.
Doesnt seem to hamper anything, but its annoying and ends up in clickhousedb
```
Log :
{"level":"warn","ts":1721622186.2458012,"caller":"clickhousemetric…
-
### What's wrong?
Hello,
I see a huge memory utilization (+ few GB) of Alloy service randomly in my environment. Sometimes it "kill" server with lower amount of RAM (~4-8GB).
I see this patte…
-
### What happened?
**Data source:** ec2 spot instance 5c.metal
This issue describes the significant different between power metrics collected on Feb and the power metrics collected on July. While …
-
### Component(s)
_No response_
### What happened?
## Description
I use otlp receiver to collect metrics from my applications and I want to use prometheus exporter in order to be able to see them i…
-
**Is your feature request related to a problem? Please describe.**
The current default configuration for the Lambda layer provides out-of-the-box support for tracing but not for metrics. Since the EM…
-
**Hello, I'm facing the following problem. I'll try to be brief. The metrics from my .net project are exported to my collector via OTLP correctly. I want to export these metrics from my collector to A…
-
### Component(s)
exporter/prometheus
### What happened?
## Description
Currently, `prometheusreceiver` [supports](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/mai…
-
in one of our four data centers, we see the following output using the exporter:
ts=2024-07-10T07:00:54.568Z caller=exporter.go:120 level=debug msg="No function handler set for metric" metric=local…
-
### Is your feature request related to a problem? Please describe.
Currently both `@opentelemetry/exporter-trace-otlp-proto` and `@opentelemetry/exporter-logs-otlp-proto` offer browser support, but…
-
Hi there,
I have tried the SW on two independent Debian 12 machines. On both, a wireguard interface is configured and working OK. Running as sudo, I get this output (regardless of verbosity set):
``…