-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the IMeterFactory approach #7087
Conversation
…n receiving a message (#7079) * Moves metrics and traces tests in dedicated folders for clarity * Adds an extension to publish and send options to start a new trace when receiving the published or sent message * add xmldocs * approval file * move * rename, and then dots and spaces, because they matter! * approval files * Change the default behavior for publishes to always break the trace Provide an API to continue the trace Use a feature with behaviors to control this behavior * Move the start/continue trace tests to files based on message operation (send/publish) * Approve API changes * Fix a test * this is handled in the publish behavior instead * revert test change --------- Co-authored-by: SzymonPobiega <[email protected]>
src/NServiceBus.Core/OpenTelemetry/Metrics/MessagingMetricsMeters.cs
Outdated
Show resolved
Hide resolved
|
||
class MessagingMetricsMeters | ||
{ | ||
public MessagingMetricsMeters(IMeterFactory meterFactory) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we keep this approach can we rename this to MessagingMetrics? Or MessagingMeters? I don't have a strong preference as long as it doesn't combine both namings
…taRegistry (#7086) * Extract old implementation with tests that fail * New implementation that passes the tests * Use the new parser * Root namespace * Simplify used types * And now without spelling errors * Array edge cases to verify whether the parsing is robust enough --------- Co-authored-by: danielmarbach <[email protected]>
…endpoint name tags (#7071) Add specific meters for recoverability actions with message type and endpoint name tags Co-authored-by: Laila Bougria <[email protected]>
string queueNameBase, | ||
string endpointDiscriminator) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two parameters sound off. They are needed down below to initialize default tags in the IncomingPipelineMetricTags, but still 🤷
…e Interfaces (#7081) * Add a test to verify the messages referencing core are scanned * Failing test for messages that reference message interfaces * Unify in one test due avoid assembly loading issues * Cleanup * AssemblyScanner should scan assemblies that reference the message interfaces assembly to make sure messages using those interfaces can be discovered and do not act like unobtrusive messages * Extract into method with a huge comment and inline hints * Add a type forwarding test as a safety net * Update src/NServiceBus.Core.Tests/AssemblyScanner/When_using_type_forwarding.cs Co-authored-by: Phil Bastian <[email protected]> * Apply suggestions from code review Co-authored-by: Brandon Ording <[email protected]> * string.Equals Co-authored-by: Brandon Ording <[email protected]> --------- Co-authored-by: danielmarbach <[email protected]> Co-authored-by: Phil Bastian <[email protected]> Co-authored-by: Brandon Ording <[email protected]>
Co-authored-by: Daniel Marbach <[email protected]>
…ied an increase in the version, that still remains 0.x since the whole metrics module is in experimental state.
…t is shorter and so cheaper.
…- this change was initially required by the code in HandlingMetricsFactory.
Fix failing tests.
…e by feature pattern for Metrics This allows removing metrics dedicated features
…discriminator info
5f93b31
to
2caf40b
Compare
… pipeline metrics.
…provider of IIncomingPipelineMetrics with the interface.
No description provided.