About Expertise Work Projects
Hosted Monitoring & Dashboards Self-Hosted Observability Stack Bulk Document Data Extraction
Free Tools
Website Health Check Email Domain Health Check DNS Health Check SSL Certificate Checker Redirect Chain Checker Robots.txt Checker XML Sitemap Validator Docker Compose Checker WordPress Security Check Downtime Cost Calculator
Blog Certifications Hire Me
// Hosted monitoring

You get the dashboard. I run the platform.

Grafana dashboards for your servers, APIs, databases or business numbers — built, hosted and maintained for you. Nothing to install, nothing to patch, and an alert when something moves.

This is not a screenshot. Open a real dashboard on the platform this project runs on, poke at it, change the time range. No signup.

Open the live demo ↗
// The problem

Most people find out from a customer

The site was down for forty minutes on Saturday. Nobody noticed, because nobody was looking, and the first report came in as an angry email on Monday morning.

Why it stays that way

  • Monitoring is a project. Standing one up properly means a stack, a server to run it on, storage, retention, upgrades and alert rules that do not cry wolf. It always loses to the work that is actually due this week.
  • The hosting bill scales badly. Commercial platforms bill per host, per seat or per gigabyte ingested, so the cost arrives before the value does.
  • The data is already there. Your server, your database and your API all expose numbers right now. Nothing is collecting them.

This project removes the first two. You give me access and tell me what matters. I build the dashboards and run the platform they live on.

// What you get

A screen you would actually open

Included in every package

  • Custom dashboards built around your systems, not a stock template with your logo on it.
  • Hosted access on my platform for 30 days, extendable at a reduced rate.
  • Per-user access so your team sees it and nobody else does.
  • Revisions after you have looked at it, because the first version is never quite the one you want.
  • Alerting to email, Slack, Teams, Telegram or a webhook, on the higher packages.
  • Documentation covering what each panel means and where the numbers come from.

What can be connected

  • Linux servers — CPU, memory, disk, network, load
  • Docker containers and their resource use
  • Websites and API endpoints — uptime, status code, response time
  • MySQL, MariaDB and PostgreSQL
  • AWS CloudWatch metrics
  • TLS certificate expiry, before the browser warning
  • Business numbers — orders, signups, failed payments, queue depth

Business metrics next to infrastructure metrics on one screen is the part people underestimate. “Orders dropped at 14:05” and “the database started swapping at 14:04” are two facts that are worth far more on the same axis than in two different tabs.

// How it works

From access to dashboard

  1. You tell me what you need to see

    A sentence is enough to start. “I want to know when the site is down and when the disk is filling up” is a complete brief.

  2. We agree the data sources and the scope

    Which systems, which numbers, which alerts, and what counts as done. In writing, before anything is billed.

  3. Access is set up

    An agent on a server, a read-only database user, a CloudWatch role, or nothing at all for an endpoint check. Read-only wherever it is possible, which is nearly always.

  4. I build the dashboards and test the alerts

    An alert that has never fired is an assumption. Each rule is triggered deliberately before handover so you know it reaches you.

  5. You get the link, the logins and the notes

    Then you use it. Revisions are included, because what you want to see changes once you have seen it.

// Packages

Three sizes

Scope is fixed per package so you know what you are buying. Current pricing and delivery times live on Upwork, where they are kept up to date.

Single Source

One system, one dashboard. Usually a server or a website.

  • One data source
  • One custom dashboard
  • 30 days hosted access
  • Revisions included
Most picked

Monitored

Two systems and alerts. The point where it starts waking you up instead of you checking.

  • Up to two data sources
  • Dashboards plus alert rules
  • One notification channel
  • 30 days hosted access
  • Revisions included

Team

Several systems, several dashboards, and people who each need their own login.

  • Multiple data sources
  • Multiple dashboards
  • Alerting with more than one channel
  • Secure per-user access
  • Written documentation
  • 30 days hosted access

Hosting continues in 30-day periods at a reduced rate after the first one. You can also see the platform itself at monitor.john-nessime.com, or read the sample handover document to see the standard of what you receive. Want to own the stack instead of renting it? That is the Self-Hosted Observability Stack.

Tell me what you need to watch.

One or two sentences is enough — what you want to know about, and what you would want to be woken up for. You get a scope, a timeline and a straight answer on whether monitoring is even the right thing to spend money on right now.

Send me a message ↓

Prefer to talk? Book a free call ↗  ·  Or hire me on Upwork ↗  ·  Typical reply within one business day.

// FAQ

Questions

What do I have to install?
Nothing on your side that you do not already have. For servers there is a small open-source agent that reports CPU, memory, disk and network. For APIs, websites and anything with a URL there is nothing at all — the platform polls the endpoint from the outside, which is also the honest way to measure it, because that is where your users are. For databases and cloud accounts it is a read-only credential scoped to metrics.
What happens when the hosted period ends?
Hosting runs in 30-day periods and extends at a reduced rate, so a dashboard you keep using does not cost the setup fee again. If you stop, the dashboards stop being served and nothing is billed silently in the background. You can also take the configuration with you and run it yourself, which is the other project on this site.
Who can see my dashboard?
Only the people you name. Access is per user, and a dashboard is private unless you ask for a public link. The demo on this page is public because I made it public as a demo. Nothing else on the platform is, and no client dashboard is ever used as an example without permission.
Can I move it to my own servers later?
Yes, and plenty of people do. The dashboards are Grafana, which is open source, so they are portable by definition rather than by favour. When you want to own the stack, the Self-Hosted Observability Stack project is that same setup deployed on your infrastructure with admin access handed to you. Starting hosted and moving later is a normal path, not a mistake.
What can actually be monitored?
Anything that exposes a number. Linux servers, Docker containers, websites and API endpoints, MySQL, MariaDB and PostgreSQL, AWS CloudWatch, and certificate expiry. Business metrics too, which people forget is possible — orders per hour, failed payments, queue depth, signups. If the number lives in a database or comes back from an endpoint, it can go on the same screen as the infrastructure.
How fast can this be running?
A single data source with a working dashboard is a matter of days, not weeks, because the platform is already built and running. What sets the timeline is how quickly the credentials and access arrive from your side. The exact delivery time per package is on the Upwork listing.
How is this different from the free tools on this site?
The free tools answer a question once, right now, for one domain. Monitoring answers it continuously and tells you when the answer changes. Run the free checks first — if they come back clean, you may not need this yet, and I would rather tell you that than sell you a dashboard.