File Upload

Loggly provides the infrastructure to amass and normalize log events and then they are available to explore interactively, build visualizations, or create threshold-based alerting. In general, any method to send logs from a organization or awarding to an external source can be adapted to send logs to Loggly. The following instructions provide ane scenario for sending logs to Loggly.

The easiest fashion to get data into Loggly for a quick examination is to upload a unmarried file. To continuously monitor a file on product systems please use file monitoring instead. File upload assumes yous are uploading text logs where each line is an consequence, with ane of our timestamp formats if y'all need timestamps, or with one of our accepted Log Types if y'all demand parsed messages. You tin send up to a maximum of 100MB per file, 1MB per event, with no timestamps or parsable timestamps within last 7 days.

The following file types are not supported:
.bin, .exe, .lib, .dat, .mp3, .gif, .jpg, .jpeg, .bmp, .zip, .gz, .tar, .dll, .png, .img, .db, .lib, .pdf, .mp4, .mpeg, .mov, .jar, .pem, .crt, .doc, .xls, .xlsx, .docx, .ppt, .pptx, .dmg, .rar, .apk, and .7z

Linux or Mac Environment

i. Send Data

Paste the following control into the terminal window, and so run it to upload the sample data to your account.

curlicue -Ten POST -T          FILE.TXT          https://logs-01.loggly.com/bulk/TOKEN/tag/file_upload

Replace:

  • FILE.TXT: enter the location of the log file you wish to read to the server
  • TOKEN: enter your customer token from the source setup page

file-upload-terminal
You should get the response ok code.

2. Verify

Search Loggly over the past hour for the file_upload tag to see your log events:

tag:file_upload

file upload

Windows Environs

1. Download ringlet

Download the latest version of cURL for apply on your Windows machine from the gyre website. Be sure to unzip the cURL files to a directory that is easy to access (east.thou. c:\curl\).

ii. Send Data

Open the Command Prompt programme from the First menu, then alter to the curl installation directory.

cd c:\ringlet

Paste the following command into the terminal window, and then run it to upload the sample data to your account.

curl -X POST -T          FILE.TXT          https://logs-01.loggly.com/bulk/TOKEN/tag/file_upload

Replace:

  • FILE.TXT: enter  the location of the log file you lot wish to read to the server.
  • TOKEN: enter your customer token from the source setup folio

3. Verify

Search Loggly over the past hour for your tag to run into your log events:

tag:file_upload

Troubleshooting

If you don't see any information in Loggly, check for these common problems:

  • Wait a few minutes in instance indexing needs to catch up
  • Check the search folio over the past solar day in case the timestamps are different from the electric current UTC time
  • Make sure yous sent data within the limits of 100MB max file size, 1MB per event, with no timestamps or parsable timestamps within last 7 days.
  • Remember to replace the filename and your token before using the curl command
  • If yous are on Windows Server 2012/16 then you may run across the error beneath: 
    curl: (60) SSL certificate problem: cocky signed certificate in certificate chain More details here: https://curl.haxx.se/docs/sslcerts.html 			 curlicue failed to verify the legitimacy of the server and therefore could not establish a secure connectedness to it. To acquire more near this state of affairs and how to set it, please visit the web page mentioned to a higher place.

    To gear up this, you accept to download the cacert.pem file from this link and then yous should re-create this file to the location where your curl.exe file exists. Side by side you have to rename the cacert.pem file to "curl-ca-packet.crt". Make certain your curl.exe and this document file remain in the same folder. Now simply retry sending logs using whorl and you lot should run across the response below:

    {"response" : "ok"}

Still Not Working?

  • Search or post your own question in the community forum.

The scripts are not supported under whatsoever SolarWinds support programme or service. The scripts are provided As IS without warranty of whatever kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a detail purpose. The take chances arising out of the use or performance of the scripts and documentation stays with you. In no result shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any amercement whatsoever (including, without limitation, damages for loss of business profits, business organisation interruption, loss of concern data, or other pecuniary loss) arising out of the use of or inability to employ the scripts or documentation.