Add basic telemetry support in core message bus implementation #73
Labels
enhancement
New feature or request
Comments
kzu
added a commit
that referenced
this issue
Nov 18, 2022
Adds core Execute/Notify and CreateMapper telemetry. Also provides telemetry when notifying subjects. The messaging "protocol" is specified as the assembly for the message type, and the protocol version, the assembly version. This will allow querying/tracking contracts being used. Operations for Execute methods are `process` and for notify/onnext, `send` (since they are fire&forget notifications). A new console app sample that showscases the features is also provided. Closes #73
kzu
added a commit
that referenced
this issue
Nov 18, 2022
Adds core Execute/Notify and CreateMapper telemetry. Also provides telemetry when notifying subjects. The messaging "protocol" is specified as the assembly for the message type, and the protocol version, the assembly version. This will allow querying/tracking contracts being used. Operations for Execute methods are `process` and for notify/onnext, `send` (since they are fire&forget notifications). A new console app sample that showscases the features is also provided. Closes #73
kzu
added a commit
that referenced
this issue
Nov 19, 2022
Adds core Execute/Notify and CreateMapper telemetry. Also provides telemetry when notifying subjects. The messaging "protocol" is specified as the assembly for the message type, and the protocol version, the assembly version. This will allow querying/tracking contracts being used. Operations for Execute methods are `process` and for notify/onnext, `send` (since they are fire&forget notifications). A new console app sample that showscases the features is also provided. Closes #73
kzu
added a commit
that referenced
this issue
Nov 19, 2022
Adds core Execute/Notify and CreateMapper telemetry. Also provides telemetry when notifying subjects. The messaging "protocol" is specified as the assembly for the message type, and the protocol version, the assembly version. This will allow querying/tracking contracts being used. Operations for Execute methods are `process` and for notify/onnext, `send` (since they are fire&forget notifications). A new console app sample that showscases the features is also provided. Closes #73
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should provide telemetry following the general guidelines for activity naming, as well as the messaging recommended tags as appropriate.
Example:
The text was updated successfully, but these errors were encountered: