Sending Data

General Methods of System Configuration to Send Data

With Loggly, you can configure standard system protocols, i.e. your current infrastructure, to send logs to our service. No need to install any proprietary agents to send logs to us.

There are a few general methods of sending logs that we’ll break down in further detail in this documentation. Each have their pros and cons:


Log Forwarding – system logs Most systems already have a log forwarding agent installed. Depending on the configuration, logs may be buffered through collector servers or sent directly from system/application servers. There are many ways to configure forwarding – we’ll walk you through the best methods.
File-watching – application logs Some applications can’t write directly to your forwarding agent. Instead, you can write to a log file that is “watched” by your forwarding agent. When there is a change to the log file(s), e.g. when an event is added, the change is forwarded to Loggly.
Bypassing syslog – application logs In rare cases, you may not have access to the local forwarding agent. In this case, the application can be configured to write log events directly to Loggly over HTTPS.
Tracking gif (Tracking pixel) Tracking pixels are commonly used by web analytics services to track site/application activity. By inserting a 1×1 pixel (.gif) on your web page, HTTP logs can be sent directly to Loggly. Any additional query string parameters can be included, which become the log event.
Log Posting This method allows you to send a one-time group of logs to us. We’ll show you how to set up HTTP POSTs.
Thanks for the feedback! We'll use it to improve our support documentation.