[BUG] Hertzbeat Notification Webhook not working
Is there an existing issue for this?
- [x] I have searched the existing issues
Current Behavior
I want to push an alert through a notification webhook.
I use Microsoft Flows webhook url like that:
https://default83781ccceezsa69b2bb58aebc1.f6.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/160bf5e83835sdffsdfg88b0516917c5d430/triggers/manual/paths/invoke/hertzbeat?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=UejZsrJyaZwwAm_jArn7Ze0PIfbdfgE4FTXUBvLDY
Hertzbeat seems to invoke the URL without the querystring, and therefore the call is denied.
How can I make Hertzbeat to invoke the complete URL.
Expected Behavior
The URL should be used entirely, and not just the 'page' url without the querystring
Steps To Reproduce
Creates a notification webhook with an URL with a querystring.
The call is made without the querystring.
Environment
HertzBeat version(s): 1.7.3
Debug logs
No response
Anything else?
[WebHook Notify Error] 401 on POST request for "https://default83sdf69b2bb58aebc1.f6.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/160bf5e83835428788b0516sdf30/triggers/manual/paths/invoke/hertzbeat": "{"error":{"code":"AuthorizationFailed","message":"You do not have permissions to perform action 'run' on scope '/triggers/manual/paths/invoke/'. Verify you are making the request with the appropriate HTTP method. See http://aka.ms/logic-trigger for details."}}"
Is there anyone working on this issue? If no one is working on it, can you assign it to me?
Hi, @mengnankkkk Welcome to submit your PR. The maintainer may assign it to you later.
Hi
I have tried to use the Nightly docker build to test de the fix but it still does not work. May be it is not in this branch :-(
Any idea on the release ?
hi the Nightly is use the master branch.
Hi
I have tried to use the Nightly docker build to test de the fix but it still does not work. May be it is not in this branch :-(
Any idea on the release ?
I did a simple local test, and it worked fine with a length of 500 characters. The previous issue was due to database limitations causing truncation; try changing those limitations.