Skip to content
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

Dingding notifier is not supporting robot with sign #44516

Open
ctwkongmu opened this issue Jan 27, 2022 · 2 comments
Open

Dingding notifier is not supporting robot with sign #44516

ctwkongmu opened this issue Jan 27, 2022 · 2 comments
Assignees
Labels
area/alerting/notifications Issues when sending alert notifications effort/none prio/medium Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@ctwkongmu
Copy link

What happened:
When create a new alerting channel to dingding robot with sign for its security setting, grafana fails to fire test notification to dingding.

What you expected to happen:

After click on test in the new alerting channel page in grafana, a testing message should appear in the dingding channel.

How to reproduce it (as minimally and precisely as possible):

  1. Create dingding robot on a channel with sign(加签) as its security setting
  2. Copy access url
  3. Go to grafana and add alerting channel.
  4. Add channel with the access url as follow
    image
  5. Click test button at the bottom
  6. On the right top corner, it says "notification sent"

Then nothing happens

Anything else we need to know?:

Seems in the source code grafana is not adding timestamp and sign as query strings in the rendered url.
https://github.com/grafana/grafana/blob/main/pkg/services/alerting/notifiers/dingding.go

Environment:

  • Grafana version: v7.4.3 (010f20c1c8)
  • Data source type & version:
  • OS Grafana is installed on: EC2
  • User OS & Browser:
  • Grafana plugins:
  • Others:
@dsotirakis dsotirakis added the area/alerting/notifications Issues when sending alert notifications label Jan 27, 2022
@idafurjes
Copy link
Contributor

@ctwkongmu Could you provide the error stacktrace?

@alexweav alexweav added prio/medium Important over the long term, but may not be staffed and/or may need multiple releases to complete. effort/none labels Apr 22, 2022
@Ariesly
Copy link

Ariesly commented Aug 30, 2023

There is no place to configure the secretKey.

The implementation related is similar to uptime-kuma.
dingding.js#L54

image

The following is the relevant explanation from the official documentation.
https://open.dingtalk.com/document/robots/custom-robot-access

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alerting/notifications Issues when sending alert notifications effort/none prio/medium Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Status: Backlog
Development

No branches or pull requests

6 participants