feat: add specification for messaging latencies

[kjschnei001]

trafficstars

Fixes #792

Changes

This PR introduces the a metric for messaging systems to report the time difference from which a message was produced to when it was consumed. This is a pretty typical business metric used to indicate the health of an asynchronous messaging system.

Merge requirement checklist

• [x] CONTRIBUTING.md guidelines followed.
• [x] 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]
• [n/a] schema-next.yaml updated with changes to existing conventions.

[kjschnei001]

I appreciate all the wonderful collaboration going on here. Quick logistical note that I will continue to be afk for the next week and a half, but I look forward to incorporating all the feedback upon my return.

[pyohannes]

Given the current messaging metric naming conventions of messaging.<operation type>.[duration|message], I wondered whether it's applicable to have a "synthetic" operation type called "enqueued", then we could have the metric messaging.enqueued.duration for the latency (the duration a message was enqueued), and messaging.enqueued.messages for the lag (this would be an UpDownCounter).

[github-actions[bot]]

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

[github-actions[bot]]

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

[github-actions[bot]]

Closed as inactive. Feel free to reopen if this PR is still being worked on.