-
### Component(s)
processor/transform
### Is your feature request related to a problem? Please describe.
When working with complex data and/or a complex sequence of statements, it can be difficult t…
-
### Component(s)
processor/tailsampling
### Describe the issue you're reporting
In [tailsampling readme](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/…
-
### Component(s)
processor/attributes
### What happened?
## Description
The attributes processor offers configuration options specific to traces or metrics.
When using a trace-only configuratio…
-
### Component(s)
processor/tailsampling
### Is your feature request related to a problem? Please describe.
We would like to use tail-based sampling because we believe it will give better insi…
-
### 🐛 Describe the bug
After running the following script trace profiler seg faulted on torch nightly:
```
import torch
import torchvision.models as models
from torch.profiler import profile, rec…
-
We should change the NewNopSettings to accept a `component.Type` to ensure in tests and everywhere we pass to factories only settings with IDs that match their Type.
**Alternative**
(which may no…
-
### Component(s)
exporter/prometheus
### What happened?
## Description
We are implementing a pipeline where we:
generate span metrics with spanmetrics plugin --> exposing the metrics with prometh…
-
### Description
In version 0.67.1 I was able to get the Task Executed / ended event from opentelemetry. However, in the most recent version, the task ended/ task executed event is not getting emitted…
-
SourceMod: 1.12.0.7146
MetaChatProcessor: 24w24a
Chat-Processor: 2.2.3
Setting `"Drixevel" "1"` in Compatibility causes chat-processor to error:
L 10/18/2024 - 14:05:28: [SM] Exception repo…
-
Forking off from #14287 …
## arch
* Refactor the traceprocessor flow. In short: determine the "inspected" pids/frames in one pass before doing all the subsetting.
* Verify we handle metric calcul…