-
## Bug Report
**Describe the bug**
The `diskstats` metric is reporting incorrect very large floating-point values for most metrics.
**To Reproduce**
Using the below config,
```
$ cat $PWD/fl…
spthm updated
1 month ago
-
-
Performed a routine helm upgrade from chart version 0.65.1 to 0.68.1 after the upgrade created Open Telemetry collector will not start. No errors in the operator - the collector errors and Crashloops…
-
**Is your feature request related to a problem? Please describe.**
Currently, monitoring and alerting on the `liveness_livenodes` metric from `_status/vars` results in too many false positives, espec…
-
**Describe the bug**
Nodes menu item should show each node with it's cpu, mem and disk usage. This should take metrics right from `kubectl top nodes`, but it's not frequently updated.
**To Reprod…
-
**Describe the bug**
In Prometheus based monitoring systems, metrics with high cardinality (big combination of unique labels) creates issue.
**To Reproduce**
When we pull metrics we'll get some…
-
- **Package Name**: @azure/monitor-opentelemetry
- **Package Version**: 1.7.0
- **Operating system**: Azure Function App
- Is the bug related to **documentation** in
- [ ] SDK API docs on https:…
-
I am using kubernetes version
Client Version: v1.22.0
Server Version: v1.24.1
I have installed metrics server by using below command and URL.
kubectl apply -f https://github.com/kubernetes-…
-
### 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…
-
would make it possible to debug broken nodes
not obvious how to do it