What Our Monitoring Covers
"The site loads" is only the most basic check. We watch several layers at once:
- Availability: whether the website, API and payment page respond from several locations, and whether the SSL certificate or domain registration is about to expire.
- Speed: how long key pages take to load and whether that is getting worse over time.
- Code errors: failures users actually see, such as a payment that returned an error or an account page that didn't load, tracked for example with Sentry.
- Server resources: CPU, memory, disk, database connections and background job queue length.
- Business metrics: for example, if no orders come in for an hour during business hours, that is a reason to check whether everything is working.
After every serious incident, we identify the root cause, document what happened and propose changes to prevent a repeat.
Choosing the Right Level for Your Site
Any website that generates leads or sales needs at least basic uptime and certificate monitoring. It is inexpensive and saves you from the nastiest surprises. Deeper monitoring with error and resource tracking is for ecommerce stores, online services, portals with user accounts and mobile apps with their own backend. For large systems, it is an essential part of high-load project support, because without data there is no way to tell what is slowing things down.
If you have a small brochure website, we won't push dozens of dashboards where a single check and an email or Slack alert will do. We match the tools to the project: external uptime services such as UptimeRobot for smaller sites, Prometheus and Grafana or Zabbix for complex infrastructure, centralized logs when you run several servers. If the project is in the cloud, we use the provider's built-in tools where possible so you don't pay twice.
Alerts Without the Noise
The most common problem isn't a lack of alerts but too many. When a phone buzzes twenty times a day over minor issues, people stop responding. So we split alerts into levels. Critical ones, such as site down or payments failing, go to the alert channel immediately, at any hour; the team responds per SLA during business hours and on individually agreed terms outside them. Warnings, such as a disk three-quarters full, go to a work channel and are handled during the day. Minor items roll up into a digest that we review periodically.
What Happens When an Alert Fires
An alert only matters if someone knows what to do with it. Along with the setup, we agree on:
- who gets the alert first and who steps in if the first person doesn't respond;
- what to check first for each type of failure;
- how and when to notify you, the business owner, and whether customers need to be informed;
- how to record the root cause after recovery.
We test this chain with a simulated outage before we hand it over. We don't promise your site will never go down, but you will know exactly how long it ran without interruption and can decide based on numbers.
What to Prepare on Your Side
- A list of pages and features your business can't run without: checkout, payments, lead forms, account login.
- Access to the server, code or cloud account if deeper monitoring is needed.
- A list of people who should receive alerts and their preferred channels.
- Information about peak hours and planned maintenance, so they don't trigger false alarms.
- A history of recent outages: what broke, for how long and how you found out.
If some of this is missing, basic checks can start right away and the rest can be added later.
What Affects the Cost
- Number of systems and checks: one website or several services, servers and integrations.
- Depth: uptime only, or code errors, resources, logs and business metrics too.
- Tools: subscription-based services or self-hosted monitoring systems that need to be deployed and maintained.
- Response: alert setup only, or our incident response and resolution per SLA as well.
Frequently asked questions
Can monitoring be set up without server access? Partially. External uptime checks work without access, but to see errors and resources, we need access to the code or server.
Who will respond to alerts? That is up to you. We can set up monitoring for your team only, or respond ourselves as part of technical support: per SLA during business hours, on individually agreed terms outside them.
Will monitoring slow down the site? No, not if it is set up correctly. Checks and metric collection create very little load compared to regular visitors.
Why track business metrics if the site loads? Because the site can load while orders fail to go through due to a payment or shipping issue. Orders dropping to zero during business hours is often the first and most reliable sign of such a problem.
Does monitoring work for mobile apps? Yes. We monitor the backend the app talks to and collect errors from the app itself to spot failures on specific devices.
Where will alerts be sent? To the channels your team uses, such as Slack, email or SMS, with different severity levels so important signals stand out.
Why Promodex
Promodex has built and supported websites since 2015, so we know which signals matter to a business and which are noise. When our in-house team supports your site, alerts go to the same developers who fix the issue, so nothing is handed off between contractors. Monitoring pairs well with website support and backups.