Monitor your NGINX server with one single command.

Powerful monitoring, without the setup complexity. No configuration headaches. Clear fixed pricing. 
curl -fsSL https://simpleobservability.com/install.sh | sudo bash -s -- <SERVER KEY>
Get Started
No credit card required

What you can monitor

NGINX monitoring covers the metrics exposed by the stub_status module and your access logs, so you get a full picture of how your web server handles traffic.

Active connections
The number of active client connections at any moment. Track it over time to spot traffic spikes and capacity limits.
Requests
Total requests and request rate to understand traffic volume and catch sudden spikes or drops.
Connection states
Reading, writing, and waiting counts to see how NGINX spends its time and spot keep-alive or upstream bottlenecks.
Access logs
Access logs collected from the standard /var/log/nginx/ location so you can inspect web traffic, including request paths, status codes, and client information.

Setup

Metrics need a one-line config change. Logs are collected automatically, no setup required.

Metrics

Enable the stub_status endpoint in your Nginx config to expose metrics on localhost.
Works with existing configurations
No performance impact
Localhost only access by default 

    server {
        listen 127.0.0.1:80;
        location /nginx_status {
            stub_status on;
            allow 127.0.0.1;
            deny all;
        }
    }

Logs

Access logs are collected automatically from /var/log/nginx/. Nothing to configure.
Standard log location
Default access log format
No configuration needed

Simple Monitoring. Simple Pricing.

Pricing starts at $3/month. No hidden fees, no complexity. Just predictable costs that scale with you.
See pricing

Frequently Asked Questions

Why does server monitoring matter?
Because without it, issues go unnoticed until they become critical. Monitoring lets you spot performance bottlenecks, detect errors early, and ensure your systems and applications stay reliable. With Simple Observability, you get real-time insight into logs and metrics so you can act before problems impact your services.
What are the requirements to run the collection agent?
The Simple Observability agent is distributed as a single, self-contained binary with zero external dependencies. There’s no need for Docker, Java, or any other runtime. Because it’s fully open-source, you can also clone our repository and build the binary yourself.
Do I need to have ports open?
No inbound ports are required on your servers. The agent uses a push-only model, sending metrics and logs outbound over HTTPS (port 443) to *.simpleobservability.com. If you operate behind a corporate proxy or firewall, just allow outbound HTTPS traffic to our domain. The agent will locally buffer data if connectivity is lost and replay it once the network is restored.
Will you help me integrate Simple Observability with my setup?
Yes. If needed, we’ll guide you step by step with a real person through every part of the integration. Most setups work out of the box, but we’ll also support the less common cases where changes to the collection agent are needed.
What if I need to send data from a specific source not listed?
Yes. Whether it is a rare server OS, an unusual log format, or a custom app metric, if it can output data we’ll help you connect it. All such support will be handled by a real, experienced engineer and never by a ticket system, autoresponder, or first-level technician.
Really?!
Yes. We are not just providing a monitoring platform. We provide complete, end-to-end support for everything you run, no matter how complex or unconventional.
What we do with your data?
Metrics and logs collected by your agent are used only to power your monitoring dashboards. This data is securely stored with our cloud provider and is never sold or shared. Thanks to our open-source agent, you remain fully in control of what is collected and sent.
How long data is retained?
Data retention depends on your plan. This applies to both metrics and logs collected from your servers.
What is a metric?
A metric is a numerical measurement of your system or application performance over time (like CPU usage or memory consumption). 100 metrics is more than enough for a typical server because it allows you to track all essential health indicators and key application performance data without being overwhelmed by 'noise' or vanity metrics that don't help you solve problems.
What is log volume or a log line?
A log line (or log entry) is a single record of an event that happened on your server or within your application. Log volume is the total count of these lines. Whether you call it a 'line' or an 'entry', it represents the same unit of information used for troubleshooting and auditing.
What payment method do you accept?
We accept all major credit cards (Visa, Mastercard, American Express) and PayPal.
Can I cancel anytime?
Yes. You can cancel your subscription at any time with no questions asked. You'll continue to have access until the end of your current billing period.
Do you offer discounts on large number of servers?
Yes! For businesses monitoring more than 10 servers, please contact us to discuss custom enterprise pricing options.