Logz.io missing logs: check the account token, the region listener port, and indexing delay

TL;DR

When logs do not show up, compare the token in your shipper config against the account settings page and fix mismatches, then restart the shipper if needed. Check firewall rules against the listener IPs for your region and the right port for your method.

Steps

1. When logs do not show up, compare the token in your shipper config against the account settings page and fix mismatches, then restart the shipper if needed. Check firewall rules against the listener IPs for your region and the right port for your method. Read the shipper's own logs for send errors, and give indexing a minute before re-checking OpenSearch Dashboards.

When to use

You are seeing this: Read the shipper's own logs for send errors, and give indexing a minute before re-checking OpenSearch Dashboards. Use this skill when you run into "Logz.io missing logs: check the account token, the region listener port, and indexing delay".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official Logz.io log shipping troubleshooting docs list the checks that resolve most missing-log cases. First, confirm the account token in your shipper config matches the token in account settings, because logs sent with the wrong token never index to your account. Second, verify connectivity to the listener host for your region with the port for your shipping method, for example 5015 for Beats and Filebeat. Third, allow a few seconds to a minute for parsing and indexing before declaring data missing.

Verified resolution: When logs do not show up, compare the token in your shipper config against the account settings page and fix mismatches, then restart the shipper if needed. Check firewall rules against the listener IPs for your region and the right port for your method. Read the shipper's own logs for send errors, and give indexing a minute before re-checking OpenSearch Dashboards.

Source URL: https://docs.logz.io/docs/log-management/troubleshooting/log-shipping-troubleshooting/