-
Notifications
You must be signed in to change notification settings - Fork 0
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
Don't throw on send-only endpoints #60
Comments
This is actually the root Metrics Plugin that does this. It was assumed to be a mistake to turn Metrics on for an endpoint that literally will report no metrics. If there's a good business reason to have this switched on then we can change it pretty easily. |
I'm not sure this is safe assumption since there is a good chance that users will reuse their configuration across endpoints, enabling monitoring by default. I think it would be better to not crash the endpoint but rather log a warning instead. |
@Particular/metrics-maintainers thoughts on this? And can you move it to the Metrics Plugin repo? |
Which users will not read and then contact us why they're not getting metrics on their sendonly endpoint. |
still feels that behavior is too much driven by the actual metrics currently available. What if we add a metric which makes sense on send-only endpoints? |
I also think that we should consider the principle of least surprise. With the current feature set if we enabled monitoring for send-only endpoints we would most likely have to add some explanation in SP to indicate that there are no metrics for send-only endpoints and this is fine. In other words, enabling metrics for send-only endpoints is not only a plugin change. |
@tmasternak Do you mean something like showing an information "this is a send-only endpoint" or something similar? I do agree, that it's not only a plugin change. |
Based on Particular/docs.particular.net#4264, is there a specific reason the metrics plugin throws at startup for send-only endpoints?
I understand that as of now, the captured metrics aren't that interesting for send-only endpoints however, throwing exceptions seems to be an unexpected and unusual behavior at fist glance.
The text was updated successfully, but these errors were encountered: