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

Feat: Add new monitor type - SIP Options Reply Ping #5362

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

edman80
Copy link

@edman80 edman80 commented Nov 20, 2024

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

  • I have read and understand the pull request rules.

Description

Add SIP Options Ping monitor type using sipsak.

Type of change

Please delete any options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

Checklist

  • [x ] My code follows the style guidelines of this project
  • [x ] I ran ESLint and other linters for modified files
  • [x ] I have performed a self-review of my own code and tested it
  • [x ] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
  • [x ] My changes generates no new warnings
  • My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

@edman80
Copy link
Author

edman80 commented Nov 20, 2024

It is worth mentioning that this monitor type relies on the sipsak binary being available in the server's PATH. I understand that something similar was done with the Tailscale ping notification type - so I followed suit with some things such as adding a visual warning in the frontend and hiding the option if Kuma is running in docker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants