I'm currently scraping metrics from one of the endpoints specified in the routes definitions, specifically this endpoint:

GET    /api/status/:cluster/:consumer/:topic/:consumerType/topicSummary   controllers.api.KafkaStateCheck.topicSummaryAction(cluster:String, consumer:String, topic:String, consumerType:String)

and

The sarama package documentation doesn't clarify when Broker.Close is expected to be called, and usage in the code doesn't make it clear either.

For example, here's a Client method in the code that sometimes closes the returned broker

The official Widgets Development Guide only contains the most basic widget types as example.

There is no functional example for a Flot chart in there right now. Or is it?

Since this is one of the most useful and probably used (at leat to me) widgets it would be very helpful to extend that docum

Currently there is an inconsistency of the naming convention for the inputs. Of the ~30 inputs, there are 5 that contain the word "input" in the name of the input

Expected Behavior

A recent breakage on master for quick-install YAML was not detected until developers manually ran the quick-install YAML. One aspect is that developers can neglect to update the quick-install YAML. #10425 follows up on fixing that.

The second aspect is that we should automate deployment of the quick-install YAML from the repo during CI for basic validation that it works.

I briefly grepped fo

Checklist

• I have included information about relevant versions
• I have verified that the issue persists when using the master branch of Faust.

Steps to reproduce

Given one Faust Table, two topic Agents:

partition_no = 4

topic_1 = app.topic('topic_1', partitions=partition_no, internal=True)
topic_2 = app.topic('topic_1', key_type=str, value_type=InfoDetai

Read the FAQ first: https://github.com/edenhill/librdkafka/wiki/FAQ

Description

I didn't find any documentation related to add ACL on topics.

Something like dpkp/kafka-python@23c7123#diff-d25dfc6dcf074a098d579d711ad43630

If it is not supported, is there any workaround to add ACLs?

How to reproduce

The namedtuples in kafka.struct package need to be documented, as they are the parameters or return values of some Apis.

Trying to build under ubuntu 16.04 with go 1.10.1, and following the building instructions:

root@builder:~# go get github.com/travisjeffery/jocko
package github.com/travisjeffery/jocko: no Go files in /root/go/src/github.com/travisjeffery/jocko
root@builder:~# cd go/src/github.com/travisjeffery/jocko/
root@builder:~/go/src/github.com/tr

Is your feature request related to a problem? Please describe.
Users have no visibility into connect worker configuration in ksqldb. That means user workflow will be either:

1. Drop out of ksqldb to view the configuration file at ksql.connect.worker.config
2. If user can’t see the worker configuration, override all parameters

Describe the solution you'd like
Need to surface con

Whether the input is Go code and the output is Swagger Spec
Or whether the input is Swagger Spec and the output is Go Code

API documentation should be locked with the API implementation so that the documentation never goes stale.

We use http_server as input and http_client as one of outputs (for a part of message batch). In case when there is some error coming from http_client, benthos starts to retry this error message indefinitely (#415). However most significant, is that it stops accepting other, normal messages.

Here is the log when I first try to send message which causes http_client to get 500 error, and

Code was added in #277, but the README wasn't updated to document the new functionality.

我看到可以通过Prometheus搭建监控环境，如果有图文，更容易理解．

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

The docs for Symfony Bundle should be more explicit about extension tags when using different consume commands. I'm referring to https://php-enqueue.github.io/bundle/consumption_extension/#consumption-extension

When using the "enqueue:transport:consume" command a consumption extension needs to be registered with the tag enqueue.transport.consumption_extension (while docs currently only mentio

Youtube demo of demostrating secor on kubernetes using GCP , which should make it easier for people to get started with secor with provided helm charts and understanding notes done in README.kubernetes.md

The template properties only contain zookeeper.connect and in theory that should be sufficient to discover the brokers. In reality, while this works for the producer, the consumer will fail to connect. It would be nice to either document the need for bootstrap.servers or derive it from zookeeper.connect when not present. Rest proxy v3.3.0

Description

A comment in Consumer example states:

// partition offsets can be committed to a group even by consumers not
// subscribed to the group. in this example, auto commit is disabled
// to prevent this from occurring.

On the [next line](https://github.com/confluentinc/confluent-kafka-dotnet/blob/d0be307fece25482b096a906fe9a6931629b8e7e/examples/Consumer/Program.c