Skip to content

Add db.version and db.product as optional resource attributes #47414

@cjksplunk

Description

@cjksplunk

Component(s)

receiver/mysql

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

The receiver will soon detect the database product (MySQL vs. MariaDB) and version at connect time but does not expose this information as resource attributes on emitted log records. Without these attributes, downstream consumers cannot distinguish between MySQL and MariaDB instances or filter by server version or validate that the receiver is interpreting the version and product as expected.

Describe the solution you'd like

Add db.version and db.product as optional resource attributes, disabled by default. When enabled, the values detected at connect time are stamped on all emitted log records. Both attributes will not be enabled by default so existing deployments are unaffected.

Describe alternatives you've considered

Emitting these as record-level attributes rather than resource attributes was considered, but resource attributes are the correct semantic location for properties that describe the origin of the data rather than the event itself.

Additional context

  • Version and product detection is already implemented as part of MariaDB/MySQL multi-version support — this is purely a matter of surfacing the detected values.
  • db.product would take values such as MySQL or MariaDB.
  • db.version would reflect the server version string (e.g. 8.0.34, 10.11.7-MariaDB).

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions