[Feature] Add cold query support in UI. #13639
Description
Search before asking
- I had searched in the issues and found no similar feature requirement.
Description
With BanyanDB's lifecycle management ready, OAP begins to support hot/warm/cold queries.
UI should follow the TTL config(when cold is present), it should activate cold condition in the query. UI was using it to limit query range only.
First of all, the right top button should show Cold Excluded and Cold Only.
When Cold Only, all query should be fired with cold flag is TRUE.
In trace and log, Duration is a part of condition as well
- Log Query, https://github.com/apache/skywalking-query-protocol/blob/4fc10625ba72ef4788972b4f7991a535065d609b/log.graphqls#L74
- Trace Query, https://github.com/apache/skywalking-query-protocol/blob/4fc10625ba72ef4788972b4f7991a535065d609b/trace.graphqls#L42
- TopN Query, https://github.com/apache/skywalking-query-protocol/blob/4fc10625ba72ef4788972b4f7991a535065d609b/top-n-records.graphqls#L31
- Browser Log Query, https://github.com/apache/skywalking-query-protocol/blob/4fc10625ba72ef4788972b4f7991a535065d609b/browser-log.graphqls#L25
Metadata, on-demand logs, and profiling are always hot data, we could keep the conditions unchanged.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
- Yes I am willing to submit a pull request on my own!
Code of Conduct
- I agree to follow this project's Code of Conduct