You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing what I think is a bug configuring alert channels. In my case I'm trying to configure a webhook to trigger an Azure Logic App.
When I click on Test I get this:
In the Signoz alertmanager container I see this log:
ts=2025-02-11T14:16:06.191Z caller=api.go:814 level=error component=api version=v1 msg="API error: failed to send test message to channel (test-Test-Ernesto)" err="server_error: unexpected status code 401: <my-webhook-url>"
The strange part is that when I write a password and the remove it in the webhook configuration options, then the test works and I receive the webhook as expected:
But when I save and close the window, I get the same behavior again. That makes me think that maybe it is a problem on Signoz side when making the webhook call.
I also have tried from outside Signoz and no further authentication is required as the url already contains the api key and it accepts anonymous access.
Expected behavior
Webhook is sent successfully
Version information
Signoz version: 0.68.0
The text was updated successfully, but these errors were encountered:
Bug description
Hello,
I'm experiencing what I think is a bug configuring alert channels. In my case I'm trying to configure a webhook to trigger an Azure Logic App.
When I click on Test I get this:
In the Signoz alertmanager container I see this log:
ts=2025-02-11T14:16:06.191Z caller=api.go:814 level=error component=api version=v1 msg="API error: failed to send test message to channel (test-Test-Ernesto)" err="server_error: unexpected status code 401: <my-webhook-url>"
The strange part is that when I write a password and the remove it in the webhook configuration options, then the test works and I receive the webhook as expected:
But when I save and close the window, I get the same behavior again. That makes me think that maybe it is a problem on Signoz side when making the webhook call.
I also have tried from outside Signoz and no further authentication is required as the url already contains the api key and it accepts anonymous access.
Expected behavior
Webhook is sent successfully
Version information
The text was updated successfully, but these errors were encountered: