Use the following tips to troubleshoot problems with shipping logs to Logz.io.
First... wait a few minutes
Wait a few minutes after sending your logs to give us time to index and make them available for search. It normally happens from within seconds to one minute, but sometimes it can take longer.
Check out our status page
If Logz.io isn’t seeing data, check our status page to make sure that we are indexing your data and that all systems are operational. You should see a green, horizontal bar with "All Systems Operational" inside.
Make sure that you have connectivity from your log shipper to Logz.io listeners. Depending on your shipping method, the port may vary. You can see the required port under the Requirement section of the log shipping instructions.
To verify you are connected to our listeners, run a telnet command from the shipping computer to listener.logz.io with the port specific to your shipping method. In the example below, the port we are testing is 5000:
telnet listener.logz.io 5000
The good outcome:
Connected to listener-group.logz.io
Escape character is '^]'.
(to get out of that, type Ctrl+] and type "quit")
The bad outcome:
If you do not have a connection to listener.logz.io over the required port, please adjust your firewall and network settings to allow the communication. You can check here for the list of all the IP addresses of our listeners.
Make sure you have the correct token in your log shipping configuration
We use the account token to identify for which account the logs are intended. If your token is missing or is incorrect, your logs will not be indexed to your account. To see your token, click on the cogwheel in the top right corner. Then, in the first available "User Settings" screen, you will see a field labeled "TOKEN." This is your account token.
Now, depending on your shipping method, the token may be added to the log within the configuration, or it may be included in the URL to which the logs are being sent. Most log shipping methods that require a configuration file have the token coded into the file -- you can simply do a "find" on that file, then look for the word "token," and you should find the location for the token. If you do not have a configuration file or cannot find the token, please review the URL to which you are sending the logs. That URL may contain the token.
Once you have found the location of the token, please verify that you are using the full and correct token.
Check the shippers logs
If you have verified that you have access to our listener and are using the correct account token, the next and final step is to check the shippers' logs. Depending on the shipper, the logs are in different locations. When checking the logs, make sure that you do not see any errors and that the shipper is actually running. If there is an issue with running the shipper, narrow down the issues. If you have multiple configurations, remove or comment out extra configurations, make sure that all the paths within the configuration are correct, and that the shipper has the correct permissions to access those paths.