A client implementation for Loggly cloud Logging-as-a-Service API
A client implementation for Loggly in node.js
node-loggly library is compliant with the Loggly API. Using
node-loggly is easy for a variety of scenarios: logging, working with devices and inputs, searching, and facet searching.
Before we can do anything with Loggly, we have to create a client with valid credentials. We will authenticate for you automatically:
var loggly = require'loggly';var client = logglycreateClienttoken: "your-really-long-input-token"subdomain: "your-subdomain"auth:username: "your-username"password: "your-password"//// Optional: Tag to send with EVERY log message//tags: 'global-tag';
There are two ways to send log information to Loggly via node-loggly. The first is to simply call client.log with an appropriate input token:
client.log'127.0.0.1 - Theres no place like home'// Do something once you've logged;
Note that the callback in the above example is optional, if you prefer the 'fire and forget' method of logging:
client.log'127.0.0.1 - Theres no place like home';
If you're using Loggly's tags functionality, simply include an array of tags as the second argument to the
client.log'127.0.0.1 - Theres no place like home' 'dorothy'// Do something once you've logged;
note Tags passed into the log function will be merged with any global tags you may have defined.
In addition to logging pure strings it is also possible to pass shallow JSON object literals (i.e. no nested objects) to client.log(..) or input.log(..) methods, which will get converted into the Loggly recommended string representation. So
var source =foo: 1bar: 2buzz: 3;input.logsource;
will be logged as:
It is also possible to log complex objects using the new JSON capabilities of Loggly. To enable JSON functionality in the client simply add 'json: true' to the configuration:
var config =subdomain: "your-subdomain"auth:username: "your-username"password: "your-password"json: true;
When the json flag is enabled, objects will be converted to JSON using JSON.stringify before being transmitted to Loggly. So
var source =foo: 1bar: 2buzz:sheep: 'jumped'times: 10;input.logsource;
will be logged as:
It is possible to send arrays, which will result in one single request to Loggly.
input.log iam:'number 1' iam:'number 2'
Searching with node-loggly is easy. All you have to do is use the search() method defined on each Loggly client:
var util = require'util';clientsearch'404'// Inspect the result setconsoledirresultsevents;;
The search() method can also take an Object parameter that allows you to set additional search parameters such as: rows, from, until, etc.
var util = require'util';clientsearch query: '404' rows: 10run// Inspect the result setconsoledirresultsevents;;
See the Loggly search guide for more details on how to effectively search through your Loggly logs.
$ curl | sh
$ npm install loggly
All of the node-loggly tests are written in vows, and cover all of the use cases described above. You will need to add your Loggly username, password, subdomain, and a two test inputs to test/data/test-config.json before running tests. When configuring the test inputs on Loggly, the first test input should be named 'test' using the HTTP service. The second input should be name 'test_json' using the HTTP service with the JSON logging option enabled:
"token": "your-really-long-token-you-got-when-you-created-an-http-input""subdomain": "your-subdomain""auth":"username": "your-username""password": "your-password"
Once you have valid Loggly credentials you can run tests with vows:
$ npm test