rkvdns_examples
Healthchecks
rkvdns_examples | Healthchecks | |
---|---|---|
2 | 208 | |
0 | 7,408 | |
- | 2.8% | |
7.6 | 9.7 | |
17 days ago | 12 days ago | |
Python | Python | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rkvdns_examples
-
Monitoring your logs is mostly a tarpit
Seems defeatist to me.
1) There has to be a notion that some things are worth acknowledging as "events"; this leads to the idea that what logs contain is indicators of events. It's a fundamentally philosophical notion. It means you need to take the time to decide what constitutes an event. Hearkening to machine learning and pirates, global warming may inversely correlate with pirates but that doesn't imply causation (either way): you can't just throw statistical techniques at data looking for "hits" and think that's significant. Even if you find some indicator as the article notes it could change; so you should identify some canary indicators and event those as well.
2) Which leads to the point about "bug parts": don't rely on a specific rare indicator, or the failure to identify such an indicator. If you find high-reliability indicators great, but look for other indicators which occur more often, that can be counted, and track those. For instance an indicator that e.g. systemd is restarting /something/, and that's happening more or less frequently, and correlates with a performance observable. If it stops reporting at all, you can start with the presumption that something about logging itself changed.
At this point my philosophical disagreement with centralized logging comes to the fore: it's expensive to load stuff into Splunk. I agree, and that's why I disagree with the approach and prefer federation.
You can use the Totalizer Agent (https://github.com/m3047/rkvdns_examples/tree/main/totalizer...) to increment counters in Redis for regex-identified keys. I don't care whether you use RKVDNS to retrieve the data or something else.
-
Ask HN: How do you monitor your systemd services?
In general this evolves to a SIEM-like solution in IT or gets added to the tag menagerie in OT.
If you're focused on "notifications are bad" note that notifications are push, and pull solutions are possible. Tail logs (or journalctl) and post significant events to Redis (https://github.com/m3047/rkvdns_examples/tree/main/totalizer...) for example.
Healthchecks
-
Show HN: I built a self-hosted status page and monitoring tool for my projects
Hey mate, I'm using https://healthchecks.io/ for heartbeat monitoring my crons. It's been working flawlessly for quite some time now. The UI is super clean and easy to navigate. It's also free up to 20 monitored jobs. Note - I'm not in any way related to that project.
-
Webhooks suck, but here are alternatives
In fact, your platform (https://healthchecks.io/) is a prime example of where running customer wasm would be really excellent.
Instead of sending webhooks out to customer configured URLs, you could run a Wasm environment to execute customer code. Off hand, a good use case here is to do further inspection of the event before it gets sent off to some other system - maybe there are cases where you send false-positives and needlessly trigger external system alerts. The customer Wasm could do more introspection on the healthcheck event and make a more informed decision about how to proceed.
-
What do you use for external monitoring?
i use healthchecks.io and have been very happy
-
Show HN: OnlineOrNot – Cron Job Monitoring
Is there anything different from https://healthchecks.io/ --- a service I've been using for free for a couple years now?
-
Prioritize IPv4 over IPv6 in dual stack
Because of this block on the router, and the fact that IPv6 connections are by default preferred over IPv4, many things on the system now cannot access the internet. the only things that can access the internet are for accessing servers that ONLY support IPv4 like my mail.smpt2go or my uptime monitoring scripts for healthchecks.io.
- Ask HN: How do you monitor your systemd services?
- Show HN: Peeng – like Pingdom, but the other way around and simpler
-
Detecting and alerting for power failures
i use https://healthchecks.io/ and highly recommend it.
-
Managing re-occurring tasks - Daily/weekly/monthly
We use a heartbeat system. Basically the monitoring continuously sends an alert to a healtcheck system. If that heartbeat fails, PagerDuty sends an alert to the oncall.
-
Uptime site monitor - notification solutions for home while sleeping
i like healthchecks.io
What are some alternatives?
collectd-systemd - collectd plugin to monitor systemd services
uptime-kuma - A fancy self-hosted monitoring tool
aioredis - asyncio (PEP 3156) Redis support
cadvisor - Analyzes resource usage and performance characteristics of running containers.
gatus - ⛑ Automated developer-oriented status page
systemd-utils - Random systemd utilities
Netdata - The open-source observability platform everyone needs
ntfy - Send push notifications to your phone or desktop using PUT/POST
Sentry - Developer-first error tracking and performance monitoring
borgmatic - Simple, configuration-driven backup software for servers and workstations
Node RED - Low-code programming for event-driven applications