LúminaKite
Availability

Uptime monitoring

Availability checks should live next to certificate and domain evidence because many incidents cross those boundaries. LuminaKite monitors uptime with protocol-aware checks and turns failures, degradation and recovery into alertable incidents.

Operational outcomes

Uptime

  • Track availability for HTTP, TCP, TLS and DNS checks from monitored domains.
  • Use thresholds, retries and expected status ranges to reduce noisy alerts.
  • Measure latency and identify degraded services before they become hard downtime.
  • Keep incident and result history tied to the same domain inventory as TLS and DNS evidence.

Core capabilities

Protocol-aware checks
Create monitors for HTTP paths, TCP ports, TLS endpoints and DNS checks depending on the service.
Expected status ranges
HTTP monitors can define expected ranges such as 200-399 so redirects and intentional responses are handled correctly.
Latency and degradation
Slow thresholds make it possible to alert on degraded service quality before the endpoint is fully down.
Failure and recovery thresholds
Configure how many failed or successful checks are needed before a monitor changes state.
Incident comments
Open incidents can keep operator notes so availability events retain context during and after response.

How the module works

1

Define monitors

Choose protocol, path or port, timeout, interval, retries and expected status behavior.

2

Run scheduled checks

Workers execute checks and record status, latency, region and error details.

3

Evaluate state changes

The service updates monitors as up, down, degraded, paused or unknown based on recent results.

4

Notify and resolve

Alert channels receive down, degraded and recovered events according to monitor and organization settings.

Signals and evidence

current status: up, down, degraded, paused or unknown
latency, p50 and p95 over the last 24 hours
status code and error message
failure and recovery counters
open incident and comment history

Common use cases

Monitor customer-facing endpoints

Track the health of web applications, APIs and regional endpoints from the same inventory used for security monitoring.

Detect degraded latency

Alert on slow responses before customers experience a complete outage.

Verify infrastructure changes

Use uptime history to confirm that deployments, DNS migrations and certificate rotations did not break availability.

Frequently asked questions

Which protocols can be monitored?

The module supports HTTP, TCP, TLS and DNS monitor types.

Can I reduce alert noise?

Yes. Configure retries, failure thresholds, recovery thresholds and degradation thresholds to match the service.

Can monitors be paused?

Yes. A monitor can be paused, which keeps the configuration without generating active checks.

Does uptime integrate with alert channels?

Yes. Down, degraded and recovered events can use the same alert routing model as other LuminaKite modules.

Related modules