Srikanth Chekuri

chore: query range v3 metrics use v4 tables

1

### Summary Part of https://github.com/SigNoz/signoz/issues/4845 #### Related Issues / PR's #### Screenshots NA #### Affected Areas and Manually Tested Areas

[EPIC]: global time range improvements

1

Enhancements - [ ] https://github.com/SigNoz/signoz/issues/4321 - [ ] https://github.com/SigNoz/signoz/issues/4322 - [ ] https://github.com/SigNoz/signoz/issues/4323

Plan for ci/infra/release

9

I am starting this discussion to consolidate our thoughts/ideas and prepare a plan ahead. I have a couple of questions in my mind that I think should be brought up....

Setup GitHub Actions CI

1

TO-DO - [ ] py - [ ] rb - [ ] js - [ ] java

Imagine a trace with the following structure. op1 -> op2 -> op3 -> ... op3 10k times -> op4. In general, for such large traces, there is little to no...

please create an issue for this if not already created. reason:- * sometimes alert is created but the key is indexed later, but not enriching it uses the non indexed...

### Summary Related to https://github.com/SigNoz/signoz/issues/4673

**Description:** This pull request addresses the remote config status reporting issue discussed in #21079. Currently, there's no way to determine if the agent terminated due to an incorrect configuration. While...

Enable exception data in query range v3. This will be used in dashboards and alerts.

Do not reset the selected values for a variable when it's parent variable changes

1

Imagine you are looking at a service metrics dashboard for an env `staging` and you want to see the same for different env `prod`, now if you change the `deployment_environment`...