HTTP/S Bulk Endpoint

Our 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.

Basic

  1. Setup our HTTP/S Bulk Endpoint
  2. You can configure your application to POST data directly to Loggly at this URL. This is not a web page so don’t open it in your browser. If you prefer, we have a variety of libraries available for common programming languages or you can use the curl test below.

    http://logs-01.loggly.com/bulk/TOKEN/tag/bulk/
    

    Replace:

  3. Test Sending Data
  4. One way to test the endpoint is to curl an example with “Hello” and “World” on two separate lines, which will create two separate events. Copy this to a terminal window, insert your customer token and file name, then send the data. This example assumes you use the bash shell.

    curl -H "content-type:text/plain" -d $'Hello\nWorld' http://logs-01.loggly.com/bulk/TOKEN/tag/bulk/
    

  5. Verify
  6. After sending the event, you should see the response ok which indicates we received it.

    {"response" : "ok"}

    Verify you can find the logs in search with the bulk tag within the last 20 minutes. It may take a few minutes to index the event. If it doesn’t work, see the troubleshooting section below.

    tag:bulk

    Screen Shot 2014-04-23 at 1.06.16 PM

Advanced Options

  • HTTP/S Endpoint – for sending single events or multiline events
  • File Upload – use the bulk endpoint to upload files smaller than 5MB
  • Tracking Pixel – if you can only make GET requests use our tracking pixel
  • Loggly Libraries Catalog – we have a variety of libraries available for common languages that implement the HTTP/S interface
  • Automated Parsing – we automatically parse many types of logs including JSON and timestamps
  • Tags – our examples use the http tag but you can include your own tags
  • Encrypt Data – Just switch the URL to https to encrypt the data. The SSL handshake may increase latency. It will also use port 443 instead of port 80.
  • Encoding – By default Loggly assumes the encoding of ‘application/x-www-form-urlencoded’ and will convert data to JSON automatically. You can set encoding in your header to ‘text/plain’ to leave your data alone and store it as regular text.
  • Search or post your own question in the community forum.

Troubleshooting

Troubleshooting HTTP offers tips if you don’t see data in the verification steps.

Thanks for the feedback! We'll use it to improve our support documentation.


Top