-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Full monitor path in notifications #3798
Closed
1 task done
Labels
feature-request
Request for new features to be added
Comments
Related: #3448 |
Hey @CommanderStorm thanks, I'll do my best to submit a PR 🍻 |
7 tasks
SOwOphie
added a commit
to SOwOphie/uptime-kuma
that referenced
this issue
Dec 30, 2024
…n providers (where applicable) As noted in louislam#3798, it would be great to have the alarm notification include the full monitor path. This was done for Mattermost in louislam#3801, but not for the other notification providers. This commit replaces all other trivial occurences of monitorJSON.name with monitorJSON.pathName.
SOwOphie
added a commit
to SOwOphie/uptime-kuma
that referenced
this issue
Dec 30, 2024
…n providers (where applicable) As noted in louislam#3798, it would be great to have the alarm notification include the full monitor path. This was done for Mattermost in louislam#3801, but not for the other notification providers. This commit replaces all other trivial occurences of monitorJSON.name with monitorJSON.pathName.
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🏷️ Feature Request Type
Other
🔖 Feature description
Hi there!
When using groups to nest monitors, it would be great if the alarm notification would include the path. It often happens that we have monitors with same names (e.g. "Grafana") but they are nested under different groups (e.g. "Dev", "Stage"...). In such cases based only on the name of the monitor, there's not enough information to know which part of the infrastructure is in question.
✔️ Solution
Including the path here
uptime-kuma/server/model/monitor.js
Line 1257 in bef6a79
❓ Alternatives
No response
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: