Use these tips to troubleshoot problems with HTTP.
Wait a few minutes after sending an event to give it time to index and appear in the search results. It normally happens within seconds, but sometimes it can take longer.
If Loggly isn’t seeing data check our status page to make sure we are indexing data and search is running. You should see green dots and "All Systems Operational".
Make sure you replaced your customer token in the URL.
- TOKEN: your customer token from the source setup page
You can POST an event to Loggly using our HTTP/S endpoint.
curl -H "content-type:text/plain" -d 'HelloWorld' https://logs-01.loggly.com/inputs/TOKEN/tag/http/
For sending multiline logs, you can use Bulk endpoint.
HTTP/S Bulk endpoint is great to send larger batches of line-separated events with faster transmission speed. You can send a maximum of 5MB per batch and up to 1MB per event. You can send plaintext or any type of automatically parsed log including JSON.
curl -H "content-type:text/plain" -d $'HellonWorld' https://logs-01.loggly.com/bulk/TOKEN/tag/bulk/
Check to make sure you are using the right contentType in header.
By default Loggly assumes the contentType of ‘application/x-www-form-urlencoded’. We recommend that you set the ‘contentType’ in your header to ‘text/plain’ to leave your data alone and store it as regular text. This also supports JSON log parsing as well as plain text.
If you have your ad-blocker enabled in your browser and you are facing issues getting your logs to Loggly please try again after disabling your ad-blocker.
You can check your HTTP response code from Status code
If you are trying to use the automatic verify feature, make sure you have the http tag in case of HTTP/S Event Endpoint and have the bulk tag in case of have HTTP/S Bulk Endpoint.
If you get the error "413 Request Entity Too Large", it means your file size is larger than the limit of 5MB. Please split your file into chunks less than 5MB, or curl the file one line at a time.
Use netstat to verify HTTP has an established connection to Loggly. Specifically, check that Loggly can make a connection through your firewall on the proper port. It is 80 for HTTP, and 443 for HTTPS.
sudo netstat -taupn | grep 80
Use ping or telnet to verify if you can make an outbound connection to Loggly. If you can’t connect to it then might be a network or firewall issue.
telnet logs-01.loggly.com 80
Use tcpdump to verify data is being sent to Loggly. If you send your events in cleartext while tcpdump is running, you should be able to see them in the left hand column. You can also run tcpdump for port 80 or 443 depends on which connection you are using. It is 80 for HTTP, and 443 for HTTPS.
sudo tcpdump -A dst logs-01.loggly.com
Search Loggly for events with the tag as http over the past hour. It may take few minutes to index the event.
- Please search our community forum for more HTTP/S answers or post your own question.
When the APM Integrated Experience is enabled, Loggly shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate Loggly and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.