吴晟 Wu Sheng

I think we should search by following created time(desc) only, right? We don't have extra conditions which ppl know.

> The protocol usage process is roughly like this > > ``` > 1. Add AsyncProfiler to the service monitoring page > > 2. You can use the "queryData" interface...

You don't need a new span AFAIK. We should not put trace id in header separately, this is not by protocol.

Please fix the CI.

The menu should be just after the `advanced feature`. We could put all incoming exclusive features in this part.

> BanyanDB TTL would be the first override mechanism regardless of core TTL setup. About the details of this override, I would suggest providing `HigherScalesMetricsTTL` configuration. By default, this should...

The proto changes seem very concern. As those things are never merged. You should not be able to update those submodules.

Supported. Doc has been updated. https://skywalking.apache.org/docs/main/next/en/banyandb/ttl/

About docs, you should write `Bundled async-profiler` docs, refer to https://skywalking.apache.org/docs/main/next/en/setup/backend/backend-trace-profiling/. And update the menu to point to this new doc.

> 2 comments of mine are still not addressed, you can merge this as you wish but make sure to address later or explain why they can’t be addressed: >...