npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

uptime-monitor-sdk

v0.1.1

Published

This SDK is used on the client side to repeatedly ping the Uptime Monitor server. When the client side terminates / crashes and the server stops receiving pings, alerts will be pushed via Pushover and/or Discord.

Downloads

14

Readme

Uptime Monitor JS SDK

This SDK is used on the client side to repeatedly ping the Uptime Monitor server. When the client side terminates / crashes and the server stops receiving pings, alerts will be pushed via Pushover and/or Discord.

Usage

npm i uptime-monitor-sdk

To maintain a session

import { UptimeMonitor, type UptimeConfig } from "uptime-monitor-sdk";

const uptimeConfig: UptimeConfig = {
  host: new URL("https://uptime.example.com"),
  serviceName: 'Example',
  secondsBetweenHeartbeat: 60, // expected heartbeat. if we miss a heartbeat over 60 seconds, an alert is pushed
  secondsBetweenAlerts: 180, // every 3 minutes
  maxAlertsPerDownTime: 10, // maximum number of times you want to be alerted
  pushoverToken: "", // obtain from pushover (optional)
  pushoverGroup: "", // obtain from pushover (optional)
  discordWebhook: "" // obtain from discord (optional)
} // note: you can use either Pushover or Discord or both

UptimeMonitor(uptimeConfig).init() // notice the `init()`!

To terminate a session

// like the above code but we call terminate instead of init()
UptimeMonitor(uptimeConfig).terminate()

// for convenient, init() method returns an instance of the UptimeMonitor
const uptime = UptimeMonitor(uptimeConfig)

// some other code

uptime.terminate()

Full Example

import { UptimeMonitor } from "uptime-monitor-sdk";

function sleep(ms: number): Promise<void> {
  return new Promise((resolve) => setTimeout(resolve, ms));
}

const uptimeConfig: UptimeConfig = {
  host: new URL("https://uptime.example.com"),
  serviceName: 'Example',
  secondsBetweenHeartbeat: 60, // expected heartbeat. if we miss a heartbeat over 60 seconds, an alert is pushed
  secondsBetweenAlerts: 180, // every 3 minutes
  maxAlertsPerDownTime: 10, // maximum number of times you want to be alerted
  pushoverToken: "", // obtain from pushover (optional)
  pushoverGroup: "", // obtain from pushover (optional)
  discordWebhook: "" // obtain from discord (optional)
} // note: you can use either Pushover or Discord or both

const uptime = UptimeMonitor(uptimeConfig).init()

async function main(fn) {
  while (true) {
    console.log("Still alive....")
    const rand = Math.floor(Math.random() * 1000);

    if (rand > 900) break;

    await sleep(10 * 1000)
  }

  fn()
}

main(() => uptime.terminate())

Constructor Parameters

|Parameters|Type|Description| |---|---|---| |url|URL|The backend URL for Uptime Monitor| |serviceName|string|Name of your app or service or script (needs to be unique)| |secondsBetweenHeartbeat|number|A whole number to specify how often you want to monitor your service and correspondingly ping the backend. If the server stops receiving after this duration, it will start sending out Push Notification alerts via Pushover| |secondsBetweenAlerts|number|A whole number of how often (in seconds) you want to receive Push Notification alerts| |maxAlertsPerDownTime|number|A whole number of the max number of alerts you will receive before notification stops| |pushoverToken|string|Obtain this from pushover.net| |pushoverGroup|string|Obtain this from pushover.net| |discordWebhook|URL string|Obtain this from your Discord server|

Note: You can use either Pushover or Discord or both. Simply omit whichever you don't need.

Calling init

You need to call init() in order to do periodic pings to uptime backend!

Calling terminate

You should call terminate when the process ends or is no longer needed. This prevents you from getting unnecessary notifications.