Documentation forLoggly

Ways of Sending Data

Any sort of log data can be sent to Loggly, it just needs to be text based. Unstructured or structured logs from any application or device can be forwarded. There’s no need to install any proprietary agents to send logs to us, simple configuration of your existing infrastructure is all that it takes.

There are a few general methods of sending logs that we’ll break down in further detail in this documentation. It’s possible to send data over either Syslog (TCP,UDP,TLS) or HTTP/S. With any of the syslog methods, your customer token will need to be within the syslog header and follow our pre-defined template. With HTTP, the customer token is part of the endpoint URL.

Find the log forwarding configuration that’s right for you, or mix & match:

Sample Demo Data

Our Sample Demo Data feature simplifies on-boarding by including a new option to get started by using demo data prior to the addition of actual user log data.

If you are using Loggly with the APM Integrated Experience enabled, Sample Demo Data will not appear in the APM Integrated Experience dashboards' summary charts.

All new trial users will be presented a choice to either configure your own log data source(s) or utilize Sample Demo Data:

Selecting "Explore demo data" will take you to our Search page with sample data pre-populated and ready to use. Demo data is identifiable by the tag "DemoEvent".

Selecting "Add your own data" will take you to the standard Loggly Source Setup page where you can choose and set up your log data source(s).

Throughout your trial, you will be able to choose to keep using demo data or to connect your own log data sources. If you decide to stop using Demo Data, the data will be disabled and deleted. To delete the demo data, go to "Source Setup" and click on the "Demo data" widget.

SolarWinds Logs & Metrics Agent (Linux)

The SolarWinds Logs & Metrics Agent (also known as the SolarWinds Snap Agent) is based on Intel’s Snap Telemetry Framework, an open framework designed to simplify the collection, processing and publishing of system data through a single API. Host monitoring involves capturing data for an individual machine such as CPU, memory and disk. Installing the SolarWinds Logs & Metrics Agent allows you to easily set up your host to monitor logs in SolarWinds Loggly as well as to track basic host metrics in SolarWinds AppOptics. The agent gives you the ability to leverage one of the many plugins to collect specific metrics.

Local Syslog Agent

The most common way to forward your system & application logs to Loggly is by using a local syslog agent. Linux systems will have an agent pre-installed and it doesn’t take long to install an agent on a Windows system. After a simple configuration change, logs will stream directly to Loggly from each system. Many applications & other services can be configured to write directly to your local syslog agent, which will then forward to Loggly. Some applications can’t write directly to your syslog agent. Instead, you can write to a log file that is watched by your syslog agent. When there is a change to the log file(s), e.g. when an event is added, the change is forwarded to Loggly.

Centralized Syslog Agent

Centralizing the log data before streaming it to Loggly is also an option. This option is great for infrastructures that prefer to have limited outbound connections.  Follow the configuration steps for "Local Syslog Agent" to setup the centralized syslog agent.

Hardware Devices

Routers, firewalls, etc have log data, but have limited capabilities with where they can send the data. Point the device to a centralized syslog agent within your own infrastructure that’s capable of forwarding the events to Loggly. Here’s how you can configure a centralized syslog agent.

Direct With No Agent

If you’d rather not use syslog to send log events, it’s possible to configure applications to write log events directly to Loggly over HTTP/S using our RESTful API. Some dev languages also have logging libraries that can log directly.

Client-Side Logging

It’s possible to log events directly from the end-user’s browser or device. The Loggly RESTful API can be used to send events over POST or GET, it also allows batched events. 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.

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 the product and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.