-
The metrics API and `dstack stats` implemented in #1827 only collects metrics for Nvidia GPUs. Metrics for AMD GPUs should also be collected out-of-the-box. Unlike `nvidia-smi` that is always present …
-
## implement collecting metrics for all services.
- ocis-glauth might be a quick win because it already collects stats. we may just need to expose them correctly
- ocis-glauth together with ocis-hel…
-
When collecting metrics from kube-state-metrics v2 with the datadog agent, the DD_TAG does not seem to apply to those metrics.
Something like this:
```
datadog:
kubeStateMetricsEnabled: fals…
-
### What's wrong?
Hi, I have a configuration where prometheus.scrape collects metrics from the application endpoint. In the configuration, I have scheme = https and insecure_skip_verify = true set fo…
-
As we may want to include some discussion on the methods' performance, tracking the time taken at each step would be beneficial.
We know wandb collects some system metrics out of the box — are thos…
rswc updated
10 months ago
-
### Component(s)
target allocator
### What happened?
## Description
Not sure if this is technically a bug, but it's a bit of a footgun. Prometheus' discovery code will always return all po…
-
Currently, KubePlus tracks the following metrics by default: CPU, memory, ingress network, egress network, and storage. We should support the ability to track application-specific metrics through Reso…
-
### Problem
Netdata currently does not support monitoring Vault metrics and we now need to support this use-case.
### Description
# Key Metrics
Vault provides a /sys/metrics end point which can …
-
See #69375 for discussion.
Summary: we collects stats for `DEALLOCATE` but not for `PREPARE` statements. This is `PREPARE` has its own short circuit execution path in `connExecutor` that prevents `…
Azhng updated
5 months ago
-
The current gc-stats in the status-api is very difficult to use in metrics (total-time and total-collects).
Research other stats to offer in the status-service for gc.