Services

The services page shows every service that the agent has seen log activity for. A service is automatically created the first time the agent sends a ContextEvent with that service name.

Service list

Column	Description
Name	Service name as reported by the OTel service.name resource attribute
Last event	When the most recent ContextEvent was received (relative time, hover for exact)

Service context

Click any service to see its current state window — the rolling buffer of recent ContextEvents that Noctuary uses for incident correlation:

{
  "service": "payments-api",
  "deploy_events": [
    {
      "event_type": "deploy",
      "vendor": "argocd",
      "entity": "payments-api",
      "new_value": "syncing:a4f2c1",
      "confidence": 0.97,
      "timestamp": "2026-05-31T02:10:41Z"
    }
  ],
  "restart_events": [...],
  "saturation_events": [...]
}

The state window is keyed by TTL — events expire automatically based on their ttl_seconds value. This prevents stale context from polluting future incident correlations.

Staleness warning

If a service has not sent any events for more than 1 hour during business hours, it may indicate a problem with the agent pipeline. Check the Agents page to verify the agent is online and processing events.