cloudnative

We have a promtail configured with two scrape configs: consulagent_sd_configs & systemd-journal
Inspecting the output from the metrics at /metrics, it seems that Promtail only exposes data relevant to file-based log tailing.

There is no data about metrics that were collected via the systemd-journal target at all.
I'm not even sure if the total metrics such as

• `promtail_targets_a

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

Is your feature request related to a problem? Please describe.

BackGround

VelaQL(Vela Query Language) is a resource query language for KubeVela, used to query application-level resource status. more details refer to [doc](https://kubevela.io/docs/platform-engineers/system-operatio

看到输入支持文件，输出利用sink和pipeline可以灵活定制 ，还能限流 ，是否能充当一个pod to pod的文件传输工具？

What would you like to be added:
A Fault injection filter should provide configurable error injection capabilities, such as delay, error local reply. it is best to have more detailed routing-based configuration capabilities

Why is this needed:
Because this is the ability that is required in the testing phas

Is mushop validated against latest version of istio 1.10.x? The steps will defer from enabling kali/jageur etc which the docs is not updated.