https://github.com/collectd/collectd/blob/0b2796dfa3b763ed10194ccd66b39b1e056da9b9/src/mysql.c#L772

Hi,
As I saw in the source for the mysql plugin, the collector specifically ignors the Prepared_stmt_count variable.
I would like to have that in the output for collectd as well.
Is it possible to enable this key in the collectd mysql collector?

Unfortunately my C skills are pretty near zer

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

Is your feature request related to a problem? Please describe.
Currently, there are many errors that do not provide certain metadata. For example, TOPIC_AUTHORIZATION_FAILED does not provide the topic(s) that failed to authorize. We provide our producer with multiple brokers and use sendBatch to send to multiple topics. It appears that some messages go through to one broker but not another bu

The error message "Hostname could not be found in context. HostNamePartitioningStrategy will not work." and variable name "hostname" are weird.

ContextNameKeyingStrategy: <-- problem code

@Override
    public void setContext(Context context) {
        super.setContext(context);
        final String hostname = context.getProperty(CoreConstants.CONTEXT_NAME_KEY);
        if (hostnam

based on: https://kafka.js.org/docs/configuration and tulios/kafkajs#298
We may not have the correct settings for the JSConsumer and JSProducer. This issue is to ensure we have them up to date after nodefluent/node-sinek#154 has been merged

Similarly to #234, it would be useful to provide functions for creating test KafkaProducers.

A good first function would be one which yields somewhat sensible default RecordMetadata.

object KafkaProducer {
  def unit[F[_], K, V](implicit F: Sync[F]): F[KafkaProducer[F, K, V]] = ???
}

Likely, this would require some internal state, hence F[KafkaProducer[F, K, V]].

When draining some brokers from its topics, it could be useful to have a json_assignment that lets the user specify how to reassign topic partitions in the cluster.