Troubleshooting the Netprobe Router

Troubleshooting Copied

Use this section to diagnose common Netprobe Router problems. Start with the Diagnostic checklist, then go to the topic that matches the problem.

Important

If the following troubleshooting steps do not resolve the issue, collect the router logs and contact ITRS Support.

For YAML settings, see Configuration. For local examples, see Introduction. For TLS and authentication, see Security.

Diagnostic checklist Copied

Before you troubleshoot a specific problem, verify the following:

• The sender points to the router collector port.
• Each destination reporter has the correct hostname and port.
• Example scripts are run from the correct directory.
• examples/unix/env.sh references a valid Java binary.
• Required ports are open and not in use.
• Every network hop to ITRS Analytics supports HTTP/2 and gRPC.
• TLS trust material, if used, is valid and not expired.
• The configured credentials are valid for the target endpoint.
• Sufficient disk space is available when using store-and-forward.
• The router logs show no repeated connection, authentication, or serialization errors.

No data reaches any receiver Copied

Cause Copied

• The router is not running.
• The sender targets the wrong host or port.
• The RoutingCollector port is blocked or already in use.
• The sender started before the router was ready.

Resolution Copied

1. Run the One-to-one example to verify the basic path.
2. Check the collector port in router-config.yaml. For more information, see Routing Collector configuration.
3. Review the router console or log output for bind or startup errors.

Only one receiver receives data in a one-to-many example Copied

Cause Copied

• The route conditions do not match the expected data.
• One receiver is not running.
• One reporter points to the wrong destination port.

Resolution Copied

1. Verify the route rules in the example router-config.yaml. For more information, see Routing workflow configuration and the One-to-many example.
2. Verify that both receiver scripts are running.
3. Compare the sender output with the expected route conditions, such as gauge and log_event.

Data is lost during a receiver outage Copied

Cause Copied

• The reporter is running in best-effort mode rather than store-and-forward mode.

Resolution Copied

1. Use the One-to-many store-and-forward example instead of One-to-many.
2. Verify that the target reporter includes a storeAndForward block. For more information, see Routing Reporter configuration and Store-and-forward delivery.
3. Check that the store directory is writable and has free space.

Buffered data is not replayed after a receiver restarts Copied

Cause Copied

• The receiver has restarted on a different port.
• The store directory is not the one expected by the router.
• The buffered files were removed between test runs.
• The receiver is failing every retry attempt.

Resolution Copied

1. Verify that the receiver is listening on the same port as configured in the reporter. For more information, see Routing Reporter configuration.
2. Check that buffered files exist in the store location.
3. Review the router logs for repeated retry or connection errors.
4. Re-run the example without running cleanup.sh until you confirm that replay succeeded.

TLS connection to ITRS Analytics fails Copied

Cause Copied

• The CA or trust chain is incorrect.
• The server certificate does not match the hostname.
• An intermediate proxy or load balancer does not support HTTP/2 or gRPC over TLS.

Resolution Copied

1. Check the hostname, port, and tls settings. For more information, see Connect to ITRS Analytics using HTTPS/TLS.
2. Verify that the correct CA certificate is referenced by trustChainFile.
3. Test against the real ITRS Analytics endpoint rather than the local example receivers.

Authentication to ITRS Analytics fails Copied

Cause Copied

• The username or password is incorrect.
• The wrong credential block is in use.
• The target service expects a different account or permission set.

Resolution Copied

1. Check shared versus per-service credentials. For more information, see Configure username and password authentication.
2. Verify that the account is valid in ITRS Analytics.
3. Combine authentication with TLS to avoid debugging issues caused by unsecured transport. For more information, see Connect to ITRS Analytics using HTTPS/TLS.

Router self-monitoring does not appear in Geneos Copied

Cause Copied

• The TCP reporter is not configured or not reachable.
• The Netprobe is not listening on the expected port.
• The Gateway is not using the supplied dynamic entity mapping.

Resolution Copied

1. Use the One-to-many self-monitoring example.
2. Verify that the router’s netprobe-reporter port matches the Netprobe Collection Agent reporter port.
3. Verify that the Gateway is using gateway.setup.xml or an equivalent configuration.
4. Verify that the selfMetrics dimensions such as hostname and app are present.