0.0.10 ā€¢ Published 2 years ago

logsans v0.0.10

Weekly downloads
-
License
MIT
Repository
github
Last release
2 years ago

Installation

npm install --save logsans

Usage

Import Library

const {LogSnag} = require("logsans")

šŸ•ŗ Notice how we've named the variable LogSnag (instead of the LogSans). This allows you to not have to change your exsiting code if you have already implemented LogSnag. šŸ˜Ž

Initialize Client

const logsnag = new LogSnag(process.env.YOUR_LOG_SNAG_TOKEN);

Publish Event & Track Event

logsnag.publish({
    project: "your-logsnag-project",
    channel: "your-logsnag-channel",
    event: "Your logsnag event",
    icon: "šŸŽ‰",
    notify: true,
    logsans: true /* This property is only needed if you want LogSans to be able to notify you when this event does NOT happen. */
});

This will do two things: 1. āœ… It publishes your event to LogSnag 2. āœ… Tracks your event on LogSans so that LogSans can alert you when the event does NOT happen within the last X minutes. (X being the "frequency" set - more on that below)

Tell LogSans When to Check

Now that you are tracking your events, it is time to tell LogSans how often to check for it.

To do that, user the Create Recurring Check endpoint here:

logsnag.check({
    project: "your-logsnag-project",
    channel: "your-logsnag-channel",
    event: "Your logsnag event",
    frequency:20 /* in minutes */
});

More Documentation: https://documenter.getpostman.com/view/10930387/Uz5MFEMj

Once you create a Recurring Check, LogSans alert you if it has not detected your event in the timeframe set by the frequency property.

For Example

If frequency is set to 30 (minutes), LogSans will check every 30 minutes. If it does not detect your event, it will publish a LogSnag event telling you that it has not seen that event in the last 30 minutes.

0.0.10

2 years ago

0.0.9

2 years ago

0.0.8

2 years ago

0.0.7

2 years ago

0.0.6

2 years ago

0.0.5

2 years ago

0.0.4

2 years ago

0.0.3

2 years ago

0.0.1

2 years ago