CommanderStorm
commented
1 week ago This is kind of niche/uncommon notification provider. As the testing effort does not scale, we require such notification providers to be contributed. If you/someone else would like to contribute such a provider, here is the Contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
Looking at https://haloservicedesk.com/apidoc/resources/tickets it should be possible
If you do decide to do this, please note these two suggestions, which often push PRs back by a review-cycle:
- Ensure that the PR includes screenshots of the
DOWN/UPandtesting/cert-expiryevents. - All keys that can/should be translated are in
en.json(⇒ our translators can translate this and no merge-confilicts between weblate and master can arise)
📑 I have found these related issues/pull requests
Feature request
🏷️ Feature Request Type
API / automation options, New notification-provider
🔖 Feature description
I'd like to request HaloPSA be added to the notifications providers list.
✔️ Solution
Ideally you would be able set Uptime Kuma to raise a ticket directly inside Halo and designate what ticket type you would like it to be by specifying the Ticket Type ID from a HaloPSA. When a services comes back online the ticket type should be marked as resolved and closed.
❓ Alternatives
Used email notifications, but this generates a ticket in Halo when a service goes down and then generates a separate ticket with the service comes online again. Ideally we would want a single ticket created and updated with any changes to the service.
📝 Additional Context
None that I can think of.