cloudnative

Is your feature request related to a problem? Please describe.
As I understand, ruler now is not adding the x-org-scopeid header to the alertmanager API calls, when it sends an alert. This would be nice if someone also uses Cortex with a tenant-aware alertmanager setup.

Describe the solution you'd like
Add the tenant ID of the tenant, on which ruler executes the rules. This would also

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.

The command prints plain text:

$ vela up -f app.yaml
Applying an application in vela K8s object format...
I0516 15:45:18.123356   27156 apply.go:107] "creating object" name="first-vela-app" resource="core.oam.dev/v1beta1, Kind=Application"
✅ App has been deployed 🚀🚀🚀
    Port forward: vela port-forward first-vela-app

Looking at how mysqldump is used, I noticed the flag --skip-extended-insert. Why write INSERT statements using one-row syntax that includes only one record in one statement, if it will be much much slower than having multiple records in one INSERT statement? Specially when importing a lot of data.

每Pipeline实现多Sink存在的问题在于：
1 多Sink时，如何解决单个Sink写下游失败时的重试的问题？
2 多Sink时，如何解决不同Sink的不同拦截器配置的问题？业务侧可能会想要不同Sink下游的数据中有不同的Intercepter配置呢？

从代码看已经实现了 sink.Interceptor可以与Sink关联 这个特性。
是否借助这个特性其实就可以解决以上两个问题了？

问题1 的解法
retry interceptor 与特定的Sink关联，这样就可以在不同的Sink间做独立的重试。
此时比如2个Sink其中有一个的下游阻塞了，则重试行为是同一个pipeline的不同sink应该都阻塞。
Roadmap计划是做成这个效果吗？

问题2的解法
为不同的Sink指定不同的拦截器，这样就可以解决不同数据下游需要不同处理

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.