-
### Is this a new feature, an improvement, or a change to existing functionality?
New Feature
### Please provide a clear description of the problem this feature solves
From [this comment](https://g…
-
### What happened?
0
Hi I have kubernetes provisioned in my vagrant build using virtualbox.
See git repo
I have set the port forwarding in the vagrantfile as shown below
```
... # N…
-
**What happened**:
Upgraded to prometheus 2.52 which now is more strict about duplicates: https://github.com/prometheus/prometheus/issues/14089 (similar to https://github.com/kubernetes/kube-state-me…
-
In the current Druid operator, some Kubernetes related failures are not tracked as errors in metrics. I am planning to add those errors as well. This is the approach I am taking. Wanted to check with …
-
/kind bug
**What steps did you take and what happened:**
While playing with e2e configuration, I noticed that patterns for replacement in upstream manifests may not be applies to used manifests,…
-
### Component(s)
collector
### What happened?
## Description
I am running the opentelemetry-operator with the `--create-rbac-permissions` flag set. When a new OpenTelemetryCollector resource is…
-
### Component(s)
exporter/prometheusremotewrite, receiver/prometheus
### What happened?
## Description
Hello, since upgrade from v0.84.0 to v0.102.0, metrics related to the receiver, processor, an…
-
### Describe the bug a clear and concise description of what the bug is.
After upgrade `kube-prometheus-stack` from `56.21.4` to `57.2.1`we alerts about `PrometheusDuplicateTimestamps` start firin…
-
Tracee has metrics enabled by default, but relevant ports are not explicitly exposed so Prometheus could collect them. Only after I added
```
ports:
- name: metrics
containerPort: 336…
-
**Describe the bug**
If `kustomize build` is run with a patchesJson6902 section specifying a nonexistant target it still reports success and outputs its resources as if it worked
**Files that ca…