Add in RavenDB #1107

[thompson-tomo]

Progresses #1107

Changes

This adds RavenDB as a db system, so that it can be used in telemetry.

Usage Example

• Health Check of the connection to the db #2205 data about db & messaging checks Xabaril/AspNetCore.Diagnostics.HealthChecks#2228. The definition of a health check event is much like an exception/event and as mentioned in the semconv meeting, 28/7/25, if attributes are not listed they are implicitly opt-in. As such this is just like if you were to put db.system.name on an exception it is beneficial. In some health checks it is even possible to check the health of db's not just sever connection etc hence even more reason to leverage the db namespace to capture that data.

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[thompson-tomo]

Still Awaiting for review.

[joaopgrassi]

@open-telemetry/semconv-db-approvers can you please take a look?

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[thompson-tomo]

awaiting feedback from @open-telemetry/semconv-db-approvers

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.