-
Notifications
You must be signed in to change notification settings - Fork 21
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
Track latency metric for based on webhook #322
Comments
The webhook URL is added into its own metric label before we create a new outbound sender (there is one outbound sender per webhook): Line 172 in 1d77dc7
So we can differentiate between codes in that way. Is this what you're looking for? |
Hi @chaitanyasingla-dt, have you had a chance to look at this? Does this solve your problem? |
Hi @kristinapathak, I am still looking into this. I will get back to you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @schmidtw
There has been an addition in caduceus to track latency metrics for outbound senders.
Scenario:
Let's suppose we have multiple webhooks getting tracked and only one of them is increasing the latency of the request. If all the webhooks latency metric is getting tracked under the same name that is
code = strconv.Itoa(resp.StatusCode)
, we will not be able to identify the source of the increase in latency of the requests.cc: @Sachin4403
The text was updated successfully, but these errors were encountered: