Cijo Thomas

Results 190 issues of Cijo Thomas

Similar to https://github.com/open-telemetry/opentelemetry-rust/pull/2085, we should remove this trait/implementations from public API. The exporters can offer https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/src/metric.rs#L172-L180 `with_delta` method to switch temporality to delta from the default cumulative. This reduces a...

A-metrics

1. Show best practices. 2. Warn users about high-cardinality, and the built-in capping. 3. Iterate that MeterProvider, Meter and Instruments should be created once and re-used. 4. Call out that...

documentation/examples
A-metrics

**What are you trying to achieve?** Current spec restricts Simple/Batch processors from calling `exporter.export()` concurrently. This can be limiting in some scenarios: 1. When Exporting to [Windows ETW](https://learn.microsoft.com/en-us/windows/win32/etw/about-event-tracing), Linux [user_events](https://docs.kernel.org/trace/user_events.html)...

spec:logs
triage:accepted:ready-with-sponsor

**What are you trying to achieve?** Trying to influence Metric aggregation temporality, aggregation for histograms when using non-otlp exporting. What did you expect to see? A MeterProvider/MetricReader env variable to...

spec:metrics
triage:deciding:needs-info

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#alignedhistogrambucketexemplarreservoir has the wording "_This implementation MUST keep the **last seen** measurement that falls within a histogram bucket_". Consider the example where Delta temporarily is used. What is the reasoning...

spec:metrics
triage:deciding:community-feedback
triage:deciding:needs-info

https://github.com/open-telemetry/opentelemetry-collector/blob/main/Makefile#L174 shows v1.4.0, so the readme got stale?

Towards https://github.com/open-telemetry/otel-arrow/issues/442 Allows customizing a bit of Logs size/structure. Tracks size of payload Neither is utilized in orchestrator yet. Can do after https://github.com/open-telemetry/otel-arrow/pull/450 to avoid merge conflicts.

Parent issue #377 Originally posted in https://github.com/open-telemetry/otel-arrow/pull/420#issuecomment-2876706857 > How do we ensure the reliability, stability, and reproducibility of these performance tests? In a Kubernetes deployment, there are so many variables...

Parent https://github.com/open-telemetry/otel-arrow/issues/377 The target being tested (Collector/Arrow pipeline) should be isolated from the load generator, backend and other noise as much as possible. eg: If we have 3 node k8s...

Parent https://github.com/open-telemetry/otel-arrow/issues/377 While the load generator is running, important stats from the target should be collected. 1. No assumption about whether target already exposes these or not. (sometimes we may...