Srikanth Chekuri

Queries now can use the time range variables. The dynamic variable will do it automatically.

duplicate https://github.com/SigNoz/signoz/issues/1903

>This is how we have instrumented various frameworks, and this approach can also be done here. I am not against the idea of patching the Application class but I don't...

This is now fixed.

>They are case-insensitive, ASCII strings. It is part of the metrics specification https://github.com/open-telemetry/opentelemetry-specification/blob/ec84e5dcd77f36e79c0fe9bb1444d62be79dbb38/specification/metrics/api.md#instrument-name-syntax

The metrics API/SDK specification left room for implementation flexibility and interpretation. It says > It is unspecified whether or under which conditions the same or different Instrument instance will be...

I would suggest doing that. I am also open to the idea of SDK using the case of the first registered instrument in case of duplicates. And I think it...

The sync should also take the labels and values into account i.e. if a line with certain labels is on focus in the current panel we should try to focus/highlight...

The "auto" instrumentation by design instruments all third-party libraries that can be instrumented. People expect instrumentation to work out of the box when they rely on `opentelemetry-instrumentation`. Users shouldn't have...

Wouldn't it be easier to opt out of what you don't want than list everything you want? In my experience, the instrumentations people want to see enabled are generally large;...