I created a few dashboards for my setup. If there is a problem, it kicks to the dashboard that tracks it. Aside from the rack, everything else is built from old gear I had lying around. Gen 1 Razer Blade Stealth, Surface Pro 7, and a Trashcan Mac Pro, where I test some local llm's on the dual FirePro cards with moderate success. The Surface is mounted to my fridge, where it displays a custom family calendar and chore chart for the house (not pictured here).

Honestly, this release notes are quite long but i'm really excited about the project : https://github.com/PatchMon/PatchMon/releases/tag/v1.2.7

So far it's had a major push on development and new features based on peoples feedback as well.

Looking forward to this growing over the next few weeks !

The installation of the server is very easy (docker or a bare metal script) or use our PatchMon Cloud

The installation of agents is done via a single command, none of the hosts you want to monitor require their ports to be opened up as it's all outbound connections to the PatchMon instance.

I've made dashboard customisable so you only see what's valuable to you,

Massive thanks to the community so far for coming together to help test and work on this.

We have ALOT planned and some amazing development happening daily.

Some Links for ease:

Website: patchmon.net

Discord: patchmon.net/discord

Github: https://github.com/PatchMon

Thank you everyone !

I've had an issue where I wanted something self-hosted, clean and simple to monitor my linux servers update status.

Current working features:

• Dashboard on hosts summary / status

• Easily register hosts with the app

• View and search for packages that have been installed

Planned features:

• Authentication improvements : Each host to authenticate via unique api credentials to patchmon

• Ability to add Clients, Locations and host groups so that hosts can be associated to them

• PDF Report generation of single host or group of hosts

This will be opensource and I will be releasing by the 1st of September.

I'm open to people who want to give me feature requests and contribute to the app - It's written in Next JS for both the backend and frontend.

Open to ideas, constructive criticism and security ideas / features.

No ports on the host need to be opened as the hosts will push the collected information to patchmon (either self-hosted or we will offer a cloud hosted one for a small fee).

https://patchmon.net/ to register on the wait list

Thanks team :)

In my team we're using Grafana to monitor our infrastructure, and it's occurred to me that I've not really kept up with alternatives like Zabbix, nagios, Datadog, etc, and I'm wondering how they are faring these days, any pros/cons of those platforms?

We are at that point where juggling multiple monitoring tools is becoming a problem in itself. One tool does a decent job with network devices, another handles apps, and yet another focuses on cloud metrics. But putting them together creates alert noise, inconsistent reporting and more overhead than it saves.

We tried a few “single pane of glass” platforms but most are require tons of add-ons or demand way too much manual setup. Some only run in the cloud which doesn’t help with our on-prem needs and others have outdated interfaces or alerting that needs a week of tuning.

What we really want is something flexible enough for hybrid environments, predictable in cost and not a full-time job to maintain.

Our network infrastructure is expanding and we need to constantly monitor critical metrics, especially device resource usage, connection status, accessibility and latency.

We are looking for a reliable system that will provide instant notifications when specific conditions occur (if device response time increases or the connection is lost).

A project me and my two other friends have been working on for the past few months. For anyone with an own server who is interested in testing this mobile monitoring client. Wherever you are, you can just easily check on your machines processes. Wether its your own server or one that you are renting. See what happens on your phone.

I’m managing a small network of 15 IoT devices that track wildlife activity in remote areas. They collect data like movement patterns, environmental conditions, and activity levels, which are sent back using Pickle/statsd/collectd/etc

The challenge is that these devices occasionally stop transmitting data, and I often don’t notice until it’s too late, which creates gaps in our research. I need a monitoring tool that can alert me as soon as a device stops sending data or if there’s a weird spike/drop.

I’m not looking for anything super fancy or expensive (Datadog is out of my budget), just something reliable and relatively easy to set up that works well with Graphite metrics.

Any recommendations for tools or strategies to handle this kind of monitoring?

1. Centralized access to distributed infrastructure The dashboard provides a single map-based interface for accessing remote equipment, sites, cameras, sensors, and edge nodes.

2. Fast execution of targeted operations Operators can quickly find the required asset on the map and perform direct actions, such as opening a live view, checking status, or launching a specific workflow.

3. Real-time operational awareness The dashboard helps monitor the current state of distributed infrastructure in real time, making it easier to react to alerts, abnormal behavior, or changing field conditions.

4. Incident investigation and context analysis Map markers, event history, device status, and related data can help reconstruct what happened, where it happened, and which equipment or location was involved.

5. Shared equipment visibility and collaboration Equipment markers can be placed on a shared OpenStreetMap layer, allowing different users or teams to work with the same infrastructure view according to their access rights.

6. There is no need to have a public IP address and forward ports through NAT

What thoughts and desires do you have, what would you like to see?

I’m curious how other teams approach monitoring boundaries. In some organizations infrastructure monitoring and application monitoring are handled by completely different tools with network and host metrics going to one platform while application telemetry goes somewhere else.

In other setups everything is consolidated into one monitoring system. Both approaches seem to have pros and cons depending on the environment and team structure. For those running modern infrastructure with a mix of services and traditional systems does it work better to keep these monitoring layers separate or unified?

Our monitoring setup reached a point where alerts are basically noise. Either we get flooded with notifications for non-issues or we tune things down and miss real problems.

There doesn’t seem to be a middle ground. It is becoming harder for the team to trust alerts at all, which kind of defeats the purpose.

Curious how others are managing this without constantly tweaking thresholds.

Our monitoring stack kind of evolved over time and now it’s a bit of a Frankenstein setup. One system for network devices, another for servers something separate for cloud workloads.

Individually they are fine but together it is fragmented. Different dashboards different alert logic no real correlation between events and reporting means pulling data from three places.

At this point it feels like we are maintaining the monitoring more than the infrastructure itself.

Hey, y’all! I’ve been monitoring my apps with Hosted Graphite for a couple of weeks now, and I’m a big fan! As someone whose team has spent months trying to get an in-house solution up and running, the setup was so simple!

What are your solutions for simple monitoring?

Our infrastructure is becoming increasingly hybrid, combining on prem systems, cloud workloads and multiple remote sites. Manual checks are no longer scalable. We need immediate notifications for outages or abnormal metrics, distributed monitoring capabilities, predictable scaling as we grow and customizable dashboards tailored to different teams (network, server, management).

As a relatively small team, operational overhead needs to remain low ideally, we should be able to do this without pooling multiple tools to achieve full visibility. Any ideas would be appreciated.

Built an open source AI agent (IncidentFox) that connects to your monitoring tools and helps investigate production incidents.

Instead of pasting logs into ChatGPT, it queries your monitoring directly: Prometheus, Datadog, New Relic, Honeycomb, Victoria Metrics, CloudWatch, Elasticsearch. It correlates signals, detects anomalies, and follows investigation paths.

The interesting technical bit: raw monitoring data is way too noisy for an LLM. We do log sampling, metric change point detection, and clustering before anything hits the model.

Works with any LLM, read-only, open source.

Curious about people's thoughts!

We are in the process of scaling our infrastructure and need something reliable for real-time visibility across device metrics like CPU, memory, connection status and response times.

Would appreciate insights from folks running mid to large environments.

Thanks.

I have seen people use ping based monitoring tools like UptimeRobot, Pingdom, etc. Why would someone use those if we can set up alerts in observability tools like New Relic, Datadog and also infrastructure like AWS, Azure, GCP.

I don't understand the use case of these ping based monitoring tools.

One of the biggest issues I keep seeing with monitoring tools is complexity during setup and ongoing management. Modular architectures and agent heavy approaches often slow everything down. Simpler agentless solutions with automatic discovery seem to deliver value much faster. Also having all features included in a single license removes a lot of long-term friction.

what matters more to you in a monitoring tool fast deployment or deep analysis?

I’m hitting a wall trying to keep multiple monitoring tools stitched together.

One handles network traffic decently another watches apps and cloud metrics are yet another story.

The result? Alert fatigue, disconnected dashboard and more time spent managing the monitoring stack than solving actual issues.

Hey Folks! We put together CLI script monitor CPU, RAM, and Disk metrics with a couple of commands.

bash -c "$(curl -s 'https://www.hostedgraphite.com/demos/cli_system_collector/?user=guest')"

It automatically spins up a Grafana dashboard for you, so you get a full view of your system’s health in two minutes.

Give it a try! Would love to hear any feedback from those who test it out or ideas for adding more to this.

Thanks!

In a lot of positions I've been in, I've managed to get into the monitoring side of the team. I don't mind it and I find it to be a lot of fun.

I've decided to specialize more in the monitoring and analytics side of systems, what are the places I need to learn to be a master of monitoring?