Security News
RubyGems.org Adds New Maintainer Role
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
node-loggly-bulk
Advanced tools
A client implementation for Loggly cloud Logging-as-a-Service API
A client implementation for Loggly in node.js. Check out Loggly's Node logging documentation for more.
The node-loggly-bulk
library is compliant with the Loggly API. Using node-loggly-bulk
you can send logs to Loggly.
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('node-loggly-bulk');
var client = loggly.createClient({
token: "your-really-long-input-token",
subdomain: "your-subdomain",
//
// Optional: Tag to send with EVERY log message
//
tags: ['global-tag']
});
There are two ways to send log information to Loggly via node-loggly-bulk. The first is to simply call client.log with an appropriate input token:
client.log('127.0.0.1 - There\'s no place like home', function (err, result) {
// 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 - There\'s no place like home');
If you're using Loggly's tags functionality, simply include an array of tags as the second argument to the log
method:
client.log('127.0.0.1 - There\'s no place like home', [ 'dorothy' ], function (err, result) {
// 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: 1,
bar: 2,
buzz: 3
};
input.log(source);
will be logged as:
foo=1,bar=2,buzz=3
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 = {
token: 'token',
subdomain: "your-subdomain",
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: 1,
bar: 2,
buzz: {
sheep: 'jumped',
times: 10
}
};
input.log(source);
will be logged as:
{ "foo": 1, "bar": 2, "buzz": {"sheep": "jumped", "times": 10 }}
It is possible to send arrays, which will result in one single request to Loggly.
input.log([ {iam:'number 1'}, {iam:'number 2'} ])
$ curl http://npmjs.org/install.sh | sh
$ npm install node-loggly-bulk
$ npm run test
FAQs
A client implementation for Loggly cloud Logging-as-a-Service API
We found that node-loggly-bulk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.
Security News
Research
Socket's threat research team has detected five malicious npm packages targeting Roblox developers, deploying malware to steal credentials and personal data.