tronyx/tronitor

Bash script to work with UptimeRobot, StatusCake, HealthChecks.io, & Upptime monitoring providers

Hello World!

Just a geek who loves tech...

📰 Some info about me

• 🔭 I’m currently working on:
  • Staying sane and stress free
• 🌱 I’m currently learning:
  • Python, Kubernetes, AWS
• 👯 I’m looking to collaborate on:
  • Bash, Docker
• 🤔 I’m looking for help with:
  • Sleep, Kubernetes, AWS, Python
• 💬 Ask me about:
  • Bash, Docker, Organizr, my Repos
• ⚡ Fun facts about me:
  • I'm a Freemason and an Eagle Scout

📫 Where to find me

📈 GitHub Stats

tronitor's Issues

Run tronitor as local user

Just wondering if it's possible? I haven't gone through the code deep enough to figure out why your require it aside from getting access to /tmp

Just about to create my first monitor from the command line! Liking it so far!

Uptimerobot API limit

Is your feature request related to a problem? Please describe.
I am running 5 monitors but as Uptimerobot introduced a API rate limit (10 per minute for the free edition) I run into the message "There seems to be an issue connecting to Uptimerobot. Please try again in a few minutes." every second run. So I did a trace and I saw that even a pause/unpause for 1 specific monitor will iterate (curl) through all monitors.

Describe the solution you'd like
Would it be possible to reduce the number of api (curl-) calls? Especially when only working with single monitor-id's?

Describe alternatives you've considered

Additional context

Calling script with >/dev/null fails with "(23) Failed writing body"

Describe the issue/bug
I trying to run the script from crontab. Calling script with >/dev/null fails with "(23) Failed writing body". My crontab:
0 2 * * * backup /opt/tronitor/tronitor.sh -m UptimeRobot -p 12345678,12345679 >/dev/null 2>&1

To Reproduce
Steps to reproduce the behavior:
./tronitor.sh -m UptimeRobot -p 12345678,12345679 >/dev/null

Expected behavior
Script should be able to run through and set all coma-seperated monitors to pause/unpause. I guess it's because the CURL-call. Another option would be to implement a "silent"-option

Actual behavior
Currently only the 1st monitor passed (12345678) will be paused

Update UptimeRobot to v2 API

Need to update the portion of Tronitor for UptimeRobot to use the v2 API as the v1 API has been deprecated.

https://uptimerobot.com/api/

Creation of new Monitors for UR

Creation of new Monitors in UR does not work.
The reason for this is a wrongly defined Content Type in the curl POST operation for UR, so the JSON file is not processed correctly by UR:

Content-Type: application/x-www-form-urlencoded

To fix this issue, remove from line 1328 und 1330 in tronitor.sh the reference to this wrong Content-Type mentioned above.

btw: It would be great to create new Monitors without using a template file. Consider this as a feature request ;-)