Skip to content
Sondeon

For the CTO and the head of operations

Server monitoring service for Linux systems, with alerts agreed with you If your server runs out of disk, who finds out: you or your customer?

Every few seconds we measure the Linux machines your system runs on and alert you when something starts to go wrong. Nothing is modified on the server.

You get alerts with thresholds agreed with you and a dashboard with each machine. The scope and the setup timeline are in writing before we start.

Bluish lights out of focus, like the indicator lights of equipment seen blurred

Updated on

Who it is for

  • You found out about an outage from a customer
  • Your system runs on Linux servers nobody watches
  • You launched a system built with AI and the team has moved on

You don't need it if your team already watches its servers and responds to alerts. And today we only cover Linux: Windows and macOS are out of scope.

Finding out from a customer is finding out late

On launch day everything works. Weeks later the disk fills up, a container restarts in a loop or a certificate expires. Almost every outage gives warning first: memory climbs, the disk grows, response times get worse. If someone measures it continuously, it shows before anyone feels it.

What we watch when we monitor your systems

  • CPU, memory and machine load
  • Disk by mount point, and what grows on its own
  • Containers: consumption, restarts and health
  • Certificates, system services and clock
  • Kernel networking
  • What happens inside the data engines
  • Trend changes in each metric

More than 125 control points

How it works

  1. Meeting and written scope

    In 30 minutes we look at what machines you have and what cannot stop. Then you get in writing what is watched and the setup timeline.

  2. Setup and thresholds

    The measurement runs on each machine and we agree the threshold for each alert with you. Monitoring changes nothing on your servers.

  3. Alerts and periodic review

    We alert you with the data point that triggered the alert, and we review with you which alerts repeat and why.

What we need from you

  • Access to each Linux server you want watched
  • The thresholds that count as a problem for you
  • Who we notify when an alert fires

How we work

What you get

  1. Alerts, with thresholds agreed with you
  2. Dashboard with the state of each machine and each container
  3. History of each metric
  4. One-page executive summary for leadership

How a finding arrives

Priority: Medium

Disk filling at a steady rate

Where
Main server, log volume
Evidence
The trend of recent weeks fills it before the end of the month
Impact
The service stops when no space is left

An example of the report format, not a client's.

Shall we talk about your case?

A 30-minute meeting to see what you have and what to review first.

Book a free meeting

Expert review, automated tool or the AI itself

All three are useful, each for one thing. AI brings the volume and people bring the judgment: that is why our review uses an automated AI tool and senior developers supervise it.

See the full comparison

Hands drawing a diagram of screens joined by arrows with a marker on a small whiteboard, next to white headphones

Who reviews

The review is done by a team of senior developers, with many hours of development and of finding the mistakes AI makes when it codes. We know more than 1,200 review points. The automated AI tool goes through them, and people verify, direct and review.

Team of senior developers

José María Salido, founder of Sondeon, answers for it

  • AI brings the volume: it goes through the known review points
  • People bring the judgment: they verify every finding before it goes into the report
  • The result is explained in a meeting with your team
Who answers for it: José María Salido, on LinkedIn

Frequently asked questions

What is system monitoring?

It is continuously measuring the state of the machines your software runs on: CPU, memory, disk, containers and certificates. It lets you see that something is starting to fail before the service stops.

Which systems can be monitored?

Linux servers, with or without Docker containers: CPU, memory, disk, containers and certificates. Windows and macOS are not covered.

How is it different from installing Zabbix or PRTG?

Zabbix and PRTG are tools: someone on your team installs them, tunes the thresholds and watches the alerts. Here we handle the measurement, the thresholds and the review of repeating alerts together with you.

What do you need, and does it affect server performance?

We need access to each Linux server and to agree the thresholds with you. It has no noticeable effect: each measurement takes under half a second, measured on a production server with dozens of containers.

What happens when an alert fires, and who fixes it?

We alert you with the data point that triggered it. Monitoring measures and alerts, and changes nothing on your servers. The fix is separate: your team applies it, or we do only if you ask.

How much does server monitoring cost, and does it replace an infrastructure audit?

The 30-minute meeting is free. The rest depends on how many servers are included and on the alerts we agree on, and it is settled in writing. It does not replace one: it is a continuous health check that measures CPU, memory, disk, containers and certificates every few seconds and alerts you when the trend changes.

Other services

  • Mobile app review

    Flutter apps built with AI, tested on real iOS and Android phones by command and with touch gestures, together with their backend.

  • Public website review

    Your website's performance, visibility in search engines and in AI assistants (SEO and GEO), accessibility and security, measured on the real page.

  • Backend and API review

    The server side behind your app or your website: what the API exposes, what it protects, what headers it serves and what ends up in its logs.

  • Database review

    PostgreSQL, Redis, Elasticsearch and RabbitMQ, in read-only mode: structure, indexes, slow queries, locks and connections.

  • Deployment server review

    The server your system will run on, reviewed before you go live: who has access, what runs on it and which limits break as you grow.

  • API monitoring

    Every call to your API measured, with its latency, its error and the screen that requested it, so you know which endpoint to optimize before traffic grows.

All services

Request your free meeting

Fill in the form and we email you to set a day and a time. It is 30 minutes to see what you have and what to review first.

What should we control?

We use your details to answer your request, to be able to prove we received it and to protect the form. The privacy policy explains it in detail.