question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Configure monitors using config file (like Heartbeat)

See original GitHub issue

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn’t find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

An ability to configure monitors using configuration JSON/XML/YAML/INI/whatever file, like Heartbeat does.

Heartbeat monitor config example:

heartbeat.monitors:
- type: icmp
  id: ping-myhost
  name: My Host Ping
  hosts: ["myhost"]
  schedule: '*/5 * * * * * *'
- type: tcp
  id: myhost-tcp-echo
  name: My Host TCP Echo
  hosts: ["myhost:777"]  # default TCP Echo Protocol
  check.send: "Check"
  check.receive: "Check"
  schedule: '@every 5s'
- type: http
  id: service-status
  name: Service Status
  service.name: my-apm-service-name
  hosts: ["http://localhost:80/service/status"]
  check.response.status: [200]
  schedule: '@every 5s'

✔️ Solution

The configuration file is injected into Docker image while uptime-kuma starts and is immediately taken into action by uptime-kuma. Such a config file can be programmatically created and automatically deployed as part of a script. Then uptime-kuma can be used for uptime monitoring of complex automated deployments like for example GitLab with all its parts.

❓ Alternatives

No response

📝 Additional Context

No response

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:35
  • Comments:5

github_iconTop GitHub Comments

3reactions
unnisathyarajancommented, Oct 17, 2022

+1

2reactions
BercziSandorcommented, Aug 11, 2022

+1

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configure Heartbeat monitors - Elastic
Specify monitors either directly inside the heartbeat.yml config file, or in external dynamically loaded files located in the directory referenced by heartbeat.
Read more >
Heartbeat logging setup & configuration example | Logit.io
Elastic Heartbeat Configuration. Monitor the status of hosts at set intervals using ICMP, TCP, and HTTP. Heartbeat is a lightweight shipping agent used...
Read more >
Getting started with HeartBeat. Monitor uptime for ... - Medium
We'll use the APT repository method to install Heartbeat. Installation and configuration of heartbeat on ELK Server. Install heartbeat. sudo apt ...
Read more >
Uptime Monitoring with Heartbeat - Coralogix
Lastly to have our config file clean. Comment out everything under the field heartbeat.monitors. We will define our monitors separately. # ...
Read more >
Heartbeat Monitoring - Cronitor
Cronitor's open-source SDKs support managing the configuration of all your monitors from a single YAML configuration file, which be synced with Cronitor as...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found