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):

Some more stats for perfromace would be nice:

• Messages last minute
• Messages last hour
• Messages last 24h
• Shortest time between messages
• Min/max/average message payload size

Problem or use case

The client is currently only logging errors and warnings. For debugging purposes and during application development, it would be very useful to also have logs detailing the message flow.

Preferred solution or suggestions

TRACE level logging for incoming and outgoing MQTT control packet types, e.g., PUBLISH, SUBSCRIBE, PUBACK, SUBACK.