kotharironak

cc: @utk-spartan

This seems a similar requirement we had for time range selection (showing upto last 1 day instead of upto last 1 month). So, all these defaults need to be wrapped...

> The requirement is similar but I think this one should be more straightforward from UI perspective. If he is working with a fork, he can just add additional columns...

@jyothishjose6190 If, you are planning to deploy from a fork, change the order as well according to your requirement. But, if you are going to put it in main, would...

@buchi-busireddy you were suggesting something on this? Can you provide more details?

@jcchavezs can this issue be moved to `hypertrace` as this is a feature request?

Yes, the purpose of the existing health check was to address certain issues like checking if the overall stack is up/down. As deep health check has its own implication on...

As part of this, we can go ahead with anomaly-based alerting rule definition as it can cover basic thresholding scenarios as well. As an example, we can have the following...

Adding work items lists as part of the description and associated tickets if indivisual items need further details.

@subintp In the first phase, I was thinking of a second option. We were thinking of having either graphQL or config service's API for CRUD for alert rules. So, you...