uptimia logo
All entries

Uptimia 6.2.0: five new monitor types, escalations, and team roles

Uptimia 6.2.0 is live, and it is the biggest release we have shipped. Five new monitor types, alerting that escalates until someone acts, roles and permissions for your team, and a much more. Everything below is in your control panel now.

Five new things you can monitor

  • Cron & heartbeat monitoring. For the jobs we cannot reach from outside: your cron job, worker, queue consumer, backup script or device pings a private URL when it finishes. If the ping does not arrive on schedule, we open an incident and alert you. Schedules can be a simple interval or a cron expression, each with its own grace period.

  • API monitoring. Chain several HTTP requests into one check. Each step asserts on the status code, response time, headers, body text or JSON fields, and can pass values to later steps — sign in, take the token, call the endpoint, verify the payload. It is transaction monitoring without a browser.

  • DNS monitoring. One monitor watches a whole zone at its authoritative nameservers: reachability over UDP and TCP, answer time, SOA serials agreeing across servers, delegation and lame servers — plus record change detection, so you are told when an A, MX, NS or TXT answer changes from the baseline you approved. Healthy is not the same as correct, and this covers both.

  • Blacklist monitoring. Watches your domain, your web IP, your mail server IP and up to five sending IPs against 17 spam blacklists, and opens an incident the moment one of them lists you. A listing only clears after several consecutive clean answers.

  • Server monitoring. A lightweight agent on your Linux servers reports CPU, memory, disk, load and network every 30 seconds, with charts in the control panel and alerts on the thresholds you set, through the same contacts as every other monitor.

Alerts that escalate until someone acts

  • Escalation policies. Build a reusable ladder — alert the on-call engineer first, the rest of the team ten minutes later, the manager after thirty — and attach it to any number of monitors. Available on Professional and up.

  • Incident grouping. When several monitors on the same policy fail together, they merge into one alert group: one down notification, one ladder, one recovery notice, instead of a pager storm.

  • Acknowledgement. “I’ve got it” pauses the ladder without closing the incident, from the control panel or from a one-click link in the alert itself — no login needed.

  • Per-monitor notes. Write a note on a monitor — a runbook link, a phone number, “check the backup job first” — and it appears on the incident page, in the alert email and in the webhook payload, where whoever is responding will actually see it.

Roles and permissions for your team

  • Five roles. Owner, Admin, Editor, Viewer and Billing, enforced on the server for every request, not just hidden in the interface.

  • Scoped access. Limit a teammate to specific monitor groups so they see and manage only their own services.

  • The full matrix. A new Roles & permissions page shows exactly what each role can do, with live member counts.

  • Activity log. Every change to monitors, contacts, templates and settings is recorded with who did it and when.

Set it up once, reuse it everywhere

  • Monitor templates. Save any monitor as a template and create the next one by typing a name and a URL. Interval, locations, contacts, escalation policy and groups all carry over.

  • Location profiles. Save a set of checking locations — “Germany only”, “EU”, “North America” — and apply it to many monitors instead of picking probes one by one.

  • Maintenance windows, rebuilt. Clearer one-off and recurring windows, a preview of the occurrences before you save, and a redesigned page and dialog.

  • Branding themes. A redesigned editor for the colours and logo applied to your scheduled reports and alert emails. Professional and up.

Incidents, logs and reports

  • A logs page. Every check from every monitor type in one filterable place, deep-linkable and exportable.

  • Root cause analysis. Incident pages show the failing check next to the response, with clickable monitor names throughout the incident history.

  • Report footers now link to our own privacy and terms pages, and public report and log exports fail loudly instead of handing you a dead link.

Plans, billing and the API

  • A clearer checkout. Plans are presented against your actual usage, upgrades and downgrades run through one checkout, unused time becomes credit, and a downgrade is scheduled for the end of the period instead of taking effect immediately.

  • API v2 and new documentation. Every monitor type, including the new ones, is available over the API, monitor groups now have full create, read, update and delete endpoints, and developers.uptimia.com documents all 280+ operations.

Comments

Thanks! Your comment has been submitted and is awaiting moderation.
Something went wrong. Please try again.

No comments yet.