-
This is very basic.
I think it applies to all (S) receivers.
Thanks
-
I compared the receivers found in `dwc:eventRemarks` with the receivers in the original detections.csv. The following receivers and associated locations should not be present in the data:
```
"rec…
-
#### Is your feature request related to a problem? Please describe.
I want to set up an Alertmanager receiver. This receiver needs a bearer token included in any requests, so I'd like to set a `cre…
-
### Observed behavior
```golang
streamBatch, err := s.js.NewStream(ctx, jetstream.StreamConfig{
Name: "PUSHBATCH",
Subjects: []string{"push.batch", "push.batch.retry"},
MaxAge: 3…
-
### The purpose and use-cases of the new component
Currently the way in which OpenTelemetry semantics are mapped to those in Datadog is [documented](https://docs.datadoghq.com/opentelemetry/schema_…
-
### Component(s)
cmd/opampsupervisor
### Is your feature request related to a problem? Please describe.
Right now the supervisor merges the received config files meaning that pipeline names n…
-
**Is your feature request related to a problem? Please describe.**
In the current state, a changefeed receiver can not know, for example, all tables that may be part of a changefeed. This makes it…
-
Issue #2: Circuits.yml takes priority above this feature.
Allow multiple receivers to be added to a single switch, instead of just one.
-
The current remappers do not override the processed metrics, but they insert new metrics. In that sense, we end up having duplicated metric values but with different name. For example, `k8s.pod.cpu_li…
-
These are the known duplicate receivers:
SG-0517BBBK1111, Bookton/Seaview from projects 1/47 respectively
SG-1614BBBK1911, sugarloaf/point lepreau from projects 74/2 respectively
Lotek-270, HOFT/wi…