Include more details to the mysql.commands metric.

[bran1501]

Component(s)

receiver/mysql

Is your feature request related to a problem? Please describe.

When I enable the mysql.commands metric, it provides general use of the commands select, insert, update and delete. However, it has to provide more insight on User activity. i.e mysql.commands.alter_table, mysql.commands.drop_table, mysql.commands.rename_table, etc

Describe the solution you'd like

Provide more attributes to this metric so it could monitor more specific activity from the users.

Describe alternatives you've considered

sql_exporter and create a Query and export all this data.

Additional context

Here is an example of multiple metrics that could be included.
https://docs.splunk.com/observability/en/gdi/monitors-databases/mysql.html#metrics

[github-actions]

Pinging code owners:

• receiver/mysql: @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

@djaglowski what do you think?

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/mysql: @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[djaglowski]

mysql.commands.alter_table, mysql.commands.drop_table, mysql.commands.rename_table

These seem like reasonable additions.

Provide more attributes to this metric so it could monitor more specific activity from the users.

Are there any others besides the three mentioned above?