PagerDuty(https://www.pagerduty.com/) is widely used for on-call globally. We are welcome the contributions to support it as alarm notification channel.

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

Bug description

Header in Top Endpoint section overflows in browser with reduced width

Expected behavior

Header shouldn't overflow

How to reproduce

1. Go to SigNoz dashboard metrics page with reduced browser window width
2. Open any application
3. Top Endpoint panel header appears overflowing

Version information

• Signoz version: v0.7.1
• *Browser version

Is your feature request related to a problem? Please describe.

As of now, the compactionCycle defaults to 500ms. https://github.com/grafana/tempo/blob/2674b233d8663852f2ccc65cc47edfee36caba23/tempodb/compactor.go#L60

This gets tough to work with on local development setups where logs ar

Bug Report

Currently, the SDK allows LogRecord options to be changed after the object was being built by the LoggerFactory.
This could introduce unnecessary complexity toward different states (before/after options got updated) and making it harder to maintain.

Discussion: open-telemetry/opentelemetry-dotnet#2891 (comment)

**What is the expected behav

There was an issue in opentracing to add a scope manager, but it doesn't look like it was ever implemented opentracing/opentracing-javascript#112

What is our action item here? Should we just document on the shim that there is no scope manager so we have no shim for it?

_Originally posted by @dyladan in https://github.com/open-telemetry/opentelemetry-specification/is

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing

@thegryfon noticed that in community axios implementations, some leak contexts and you wouldn't necessarily know until a second root trace is attempted.

here's an example scenario I think tests could cover:

there is no parent trace in scope
create a client request
create a second client request
verify that both client requests are root spans

Is your feature request related to a problem? Please describe.

The .. module has a conditional dependency on the parseurl library. This library is not an agent dependency. However, if parseurl is present then the agent will use it instead of it's own home grown URL parsing.

We've had users report that this conditional `re