Skip to main content

Monitoring gaps - a service, site or signal is missing

The host is in the console and wakora doctor is green, but something you expected to see is not there. Almost every case below is visible in the agent log:

tail -f /var/log/wakora/agent.log

Connection and registration problems have their own pages: wakora doctor, Connectivity, The host does not appear.

A service is not being monitored​

The agent only activates definitions that match its facts. Check discovery:

  • Is the service actually running as a process the definition matches? A host running mod_php does not match a php-fpm definition, for example.
  • Is the port listening and owned by the expected process?

If a probe needs a credential and it is missing, the check fails with a clear message to run wakora secret set. If a probe needs a non-standard path, set a location override.

An APM capability shows "staged, awaiting activation"​

That is expected. The agent staged a change that needs a service reload and will not apply it for you, and the console has no remote-execute button by design. Copy the exact command from the "action required" card and run it during a maintenance window. The agent detects the reload and flips the capability to active. See Never restart your services.

A site is instrumented but sends no spans​

The usual causes, all of which the agent surfaces as facts on the host:

  • The site's pool runs a PHP version outside the activated set. Each site's inventory fact carries the PHP minor of its pool; a 7.x pool on a host activated for 8.x explains the silence.
  • A pool-level prepend override. A php_admin_value[auto_prepend_file] in the pool config silently beats the instrumentation ini; the agent detects and reports it.
  • A half-removed activation. If the extension line was removed but the prepend left behind, the agent reports it and stages a ready cleanup command.

RUM is enabled but no data arrives​

Injection only touches GET HTML responses that contain </head>, and it requires the APM runtime active on that site's PHP version. For sites outside the APM matrix, use the hosted snippet instead. See RUM.

Log lines I expect are not arriving​

By default only notice and above ships: errors, warnings, notices. info and debug lines, including web access logs, ship only after you opt that service into deep logging from the console. If nothing at all arrives, check whether log shipping was switched off for the service, the host, or the team. See Logs.

SNMP polling fails after a collector failover​

Secrets are never transferred between hosts. If you set the SNMP credential only on the primary collector, the backup cannot poll. Set the secret on every listed collector. See SNMP and network.

A site shows an expired certificate but visitors see a valid one​

The site is probably behind a CDN or a proxy: visitors get the edge certificate, while the agent's loopback check measures the origin certificate on your box. The agent detects this (the domain resolves away from the host) and marks the site offloaded, so it is reported as an origin-certificate housekeeping issue, not a visitor-facing emergency. See Websites and domains.

Metrics stopped, then came back with a gap filled​

That is the offline buffer working. When the connection drops, the agent spools metrics to disk and replays them on reconnect, so the gap backfills. A dead link is detected within about 30 seconds.

Checking resource usage​

The agent should sit under 1% CPU and well under 100 MB RAM. If it does not, capture the log and the output of wakora --version and open a support request.