Santosh Cheler
Santosh Cheler
Feature request - It will be good to mock server errors too - it will help a great deal in unit testing the clients. http://slowwly.robertomurray.co.uk/error/502 -- should return a HTTP...
Since the OpAmp spec includes support for configuration of Otel SDKs as well, this issue concerns applying the same protocol/workflow to client-side (RUM) SDKs (mobile apps and browser apps), which...
## Changes This PR is a follow up to the OTEP [Events and Logs API](https://github.com/open-telemetry/oteps/blob/main/text/0202-events-and-logs-api.md). It describes the specification for an Events and Logs API and also defines semantic conventions...
**What are you trying to achieve?** For client-side telemetry (mobile apps, browser apps), it's prohibitive to send spans, metrics and logs separately on different connections. I want to explore ways...
- [x] This only affects the JavaScript OpenTelemetry library - [ ] This may affect other libraries, but I would like to get opinions here first Are there any concerns...
- [x] This only affects the JavaScript OpenTelemetry library - [ ] This may affect other libraries, but I would like to get opinions here first 1. For the xml-http-request...
- [x] This only affects the JavaScript OpenTelemetry library - [ ] This may affect other libraries, but I would like to get opinions here first What work is needed...
## Changes This came up in https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/14474 where it was highlighted that just `name` is not sufficient to provide for uniqueness of a Kubernetes Event. The attribute `event.domain` is only...
Fixes #2806 ## Changes In the Client Instrumentation SIG we agreed on using only `browser.` namespace in the browser resource for identification purpose. In this PR, we are removing the...
**What are you trying to achieve?** I am trying to remove the use of `process.runtime.*` attributes for browser resource. In the Client Instrumentation SIG we agreed on using only `browser.`...