TREN

NPM Synthetic monitoring

Know a service is down before users do.

Devices can be up while users still cannot reach the website. Netronus checks your web applications, DNS records, service ports and TLS certificates on a schedule, the way a user would, shows where response time goes and warns before certificates expire.

Check types

  • AvailableHTTP / HTTPSStatus code, keyword, redirects, custom headers; DNS, connect, TLS, first byte and total time.
  • AvailableDNSQuery a server of your choice and compare the answer.
  • AvailableTCPPort connection and banner text.
  • AvailableICMPReachability, latency and loss over ping.
  • AvailableTLSCertificates on SMTPS, LDAPS, IMAPS and SMTP / IMAP / POP3 STARTTLS.

The problem

What gets in the way today

01

Green devices, broken service

Servers and switches can be fine while the application returns errors or a blank page; infrastructure monitoring does not see it.

02

Expiring certificates

An expired certificate reaches users as a security warning and an outage, and is usually noticed on the last day.

03

Where “slow” comes from

Without knowing whether the time goes to DNS, the TLS handshake or the application, fixes are guesswork.

The solution

Every check is an asset

Each synthetic check is an asset in the inventory: same alarm engine, same dashboards, same maintenance and notification rules. Checks run from the Netronus server; consecutive-failure counting keeps one-off blips from becoming alarms.

  • Response time breakdown: DNS, connect, TLS, first byte, total
  • Certificate days left, issuer and SANs; alarms 30 and 7 days before expiry
  • Outage periods and history; bulk import from CSV

Capabilities

What you get

HTTP/HTTPS checks

Expected status code, a keyword that must or must not appear, redirect following, custom headers, credential profiles; HTTP/1.1 and HTTP/2.

Time breakdown

DNS resolution, TCP connect, TLS handshake, first byte and total time are measured and charted separately.

Certificate tracking

Days left, issuer and SAN list; ready-made alarm templates 30 and 7 days before expiry and for invalid certificates.

DNS, TCP, ICMP, TLS

Queries to a specific DNS server with an expected answer; ports and banners; ping; STARTTLS certificates on mail and directory services.

Ready-made alarm templates

Down (consecutive failures), response time, certificate expiry, invalid certificate, keyword and no data.

Outage history

Outage periods, durations and last state per check; a time breakdown chart on the detail page.

Safe defaults

Cloud metadata and link-local addresses are blocked; concurrency per target and a rate limit per check are enforced.

Bulk management

Add checks from the list, a form or CSV; test a check in the form before saving it.

Technical summary

At a glance

ItemDetail
Check typesHTTP/HTTPS, DNS, TCP, ICMP, TLS (SMTPS, LDAPS, IMAPS, STARTTLS)
MeasurementsStatus, response time and its breakdown, certificate days left, outage periods
LocationThe Netronus server
AlarmsThe shared alarm engine; ready-made templates
LicensingBy number of synthetic checks; 10 checks in NPM Pro and Netronus Suite, add-on packs from +10 to +1000

Roadmap

Coming next

These items are planned and not part of the current release.

  • Roadmap POST requests and multi-step scenarios
  • Roadmap HTTP proxy support

See Netronus in your own environment

We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.