Srikanth Chekuri

I couldn't reproduce the error. Please share full response from the APIs.

How about updating the logic to only show the original attributes and updating the query builder logic to use the column in the query for those attributes which have a...

You can still show that they are indexed like logs do with the same original attribute names.

The two durations are confusing. Can we just show avg duration only?

@ankitnayan taking the same trace you linked, here you can see 10 `HTTP GET /route` under `HTTP GET /dispatch`. Now, make it 1k or 10k `HTTP GET /route` spans which...

I shared the feedback here https://signoz-team.slack.com/archives/C02TJ466H8U/p1717012138360279?thread_ts=1716785112.844369&cid=C02TJ466H8U.

Here is what I suggest - don't populate the `stepInterval` on the client side by default or automatically when the time range changes. The backend will always select the most...

The frontend changes are fine but some backend changes should be made before we merge this.

@vikrantgupta25 this change is working for alerts. please enable this across the product wherever query builder is used.

reopening the issue since the issue is not completely fixed as the previously selected time range could still be incorrect.