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

@apptrail/application-events-sdk

v0.0.10

Published

Apptrail Application Events SDK for Node JS.

Downloads

25

Readme

Apptrail Application Events SDK for Node JS

You can use the Apptrail Application Events SDK for Node JS to send audit logs from your Javascript applications to your customers.

Learn more

Notes and tips

  • Requires Node JS >= 12
  • The Application Events SDK relies on your Apptrail API key secret and is meant for server side use only and not in the browser.
  • Instantiate the client once at the top of your application and reuse it to prevent unnecessary recreation.

Installing

npm i --save @apptrail/application-events-sdk

Instantiating client

import { ApptrailEventsClient, ApptrailEventsClientConfig } from "@apptrail/application-events-sdk";

const myApiKey = loadMySecretApiKey();
const myRegion = "us-west-2";

const eventsClient = new ApptrailEventsClient({
  region: myRegion,
  apiKey: myApiKey,
});

Sending an event

import { ApptrailEvent, ApptrailEventsClient, ApptrailEventsClientConfig } from "@apptrail/application-events-sdk";

const event: ApptrailEvent = {
  tenantId: "cust_MGY4MmYzNDMtZjEwOC00OWI",
  eventName: "CreateRepository",
  eventTime: "2022-01-26T06:01:00Z",
  actor: {
    id: "acct_MmRlODllZDctM2I0Yi0",
    details: {
      type: "account",
      name: "API Access",
    },
  },
  resources: [
    {
      id: "repo_YWI5NjkzY2UtNzI1Ny00N",
      details: {
        repositoryType: "V2",
      },
    },
  ],
  context: {
    sourceIpAddress: "103.6.179.245",
    userAgent: "Apache-HttpClient/4.5.3 (Java/11.0.11)",
  },
  tags: {
    severity: "LOW",
  },
  eventDetails: {
    request: {
      repositoryName: "my-repository",
    },
  },
};

eventsClient.putEvent(event);

Handling errors

As a best practice, you should handle errors while sending events, especially if you are sending critical logs. The Events client includes automatic retries with backoff, but errors can happen due to rare server issues or client side issues.

You can choose what to do with failing events. For example, you may sideline them to disk, or a dead letter queue for retry or remediation.

import { ApptrailError } from "@apptrail/application-events-sdk";

try {
  eventsClient.putEvent(event);
} catch (e: any) {
  const error = e as ApptrailError;
  console.log(e.message);
  console.log(e.code);
  // handle error
}