cloudnative

Currently promtail supports reading logs from a Kafka topic, and write out to a Loki installation.
The feature request is for promtail to have the ability to write logs to a Kafka cluster, the reason explained below.

Describe the solution you'd like
Kafka can be found in many organisations, and is often times used as a way to have a central place for information to flow through. This so

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.

When I want to delete more than one apps, I have to do it one by one.

vela delete composed-app -y
vela delete frp-proxy -y
vela delete vela-app-with-sidecar -y
vela delete ecs-demo -y

It's annoying when I have many apps.

Describe the solution you'd like

I hope we can delete them together at once:

`

As we discussed on Discord, it will be great to have some options to dump specific tables.
By adding a new option only_tables RepliByte will only dump these tables.

This is an example of the final config file:

source:
  only_tables:
    - database: public
      table: us_states
    - database: public
      table: order_details

Here only the tables named us_states a

每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指定不同的拦截器，这样就可以解决不同数据下游需要不同处理

在pkg/adapter/dubboregistry/registry/listener.go里面有

type Listener interface {
Close()
WatchAndHandle()
}

在pkg/remote/zookeeper/client.go也有

type Listener interface {
Close()
WatchAndHandle()
}

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.