-
Notifications
You must be signed in to change notification settings - Fork 215
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
Notifications via DingTalk service sometimes unsuccessful #467
Comments
Thank you for submitting this issue, the error message Could you check if there are any such characters in your configuration file? Alternatively, kindly provide the content of your configuration file(ensuring data anonymization if needed) so that we can identify and resolve the issue. |
@samanhappy is right. Providing more information is also better. By the way, I will also do some tests to check if there are some potential bugs or compatibility issues. |
|
Could you please provide the complete configuration content to let us test it in our local enviroment? |
|
Appreciated for the thorough response, the configuration content does not include any special characters as you mentioned, I apologize for my hasty speculation. After checking the code I find that the notification content will incorporate the error message related to the probe, and it will be logged in the following format: Could you please check your enviroment for a similar log entry? I've tested the configuration, but I was unabled to reproduce the Dingtalk error. |
Some online blogs say that error 40035 is related with invalid json payload. But as i tested, easeprobe produces valid json payload which match the request of dingtalk official document. If possible, could you please add a log to |
Thank you for your reply, it's strange, I don't know what's wrong with the configuration file to configure the logging, but my corresponding directory did not find the program running log nor notification logs
|
The console displays the following logs, but no log files are found in the corresponding log directory
|
please change dry to false. dry run means the log will not be notified. |
and for |
based on the manual in https://github.com/megaease/easeprobe/blob/main/docs/Manual.md#72-notification-configuration if you want to set filed like |
Hi, i will make a pr to do that. Please wait. |
Hi, can you download the newest version of code from github and use |
Environment (please complete the following information):
Describe the bug
When using the DingTalk notification service, some exception notifications can be sent out and some cannot. The message is as follows:
WARN [2024-01-07T10:12:38+08:00] [dingtalk / Dingtalk alert service / Notification] Retried to send 1/3 - Error response from Dingtalk [%!d(float64= 40035)] - [{"errcode":40035, "errmsg": "Missing parameter json"}]
Expected behavior
The notifications either both succeed or fail, and the feedback from the DingTalk service response shows that the request is not compliant. I'm not sure what's wrong.
The text was updated successfully, but these errors were encountered: