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

@kozmoai/backstage-plugin-bugsnag

v2.2.8

Published

![a preview of the Bugsnag plugin](./docs/backstage-bugsnag-plugin.png)

Downloads

2

Readme

Bugsnag Plugin for Backstage

a preview of the Bugsnag plugin

Rate Limit

Since Bugsnag has a policy around API rate limits (https://bugsnagapiv2.docs.apiary.io/#introduction/rate-limiting), we are not displaying error trends in the table. However, you can visit error details page in Bugsnag for more details, including error trend.

Features

  • Bugsnag plugin errors overview tab.

How to add bugsnag project dependency to Backstage app:

If you have your own backstage application without this plugin, here it's how to add it:

  1. Install the plugin inside backstage/packages/app :
cd packages/app
yarn add @kozmoai/backstage-plugin-bugsnag
  1. In the app-config.yaml file in the root directory, add bugsnag to the proxy object:
proxy:
  ...
  '/bugsnag/api':
    target: 'https://api.bugsnag.com'
    headers:
        Authorization: 'token ${BUGSNAG_PERSONAL_TOKEN}'
        X-version: '2'

Define number of results fetched per request (this is optional and if ommited it will be set to default value of 30). This will be used as a 'per_page' parameter (https://bugsnagapiv2.docs.apiary.io/#introduction/rate-limiting).

bugsnag:
  resultsPerPage: <number>
  1. Add plugin to your Backstage instance:
// packages/app/src/components/catalog/EntityPage.tsx
import { EntityBugsnagErrorsOverviewTable } from '@kozmoai/backstage-plugin-bugsnag';
...

const serviceEntityPage = (
  <EntityLayoutWrapper>
    ...
    <EntityLayout.Route
      path="/bugsnag"
      title="Bugsnag">
        <EntityBugsnagErrorsOverviewTable />
    </EntityLayout.Route>
    ...
  </EntityLayoutWrapper>
);
  1. Run backstage app with yarn start and navigate to services tabs.

How to use Bugsnag plugin in Backstage:

  1. Add annotations to the yaml config file of a component:
bugsnag.com/project-key: <organization-name>/<project-name>

Note that you must use the full names, not the slugs.

These values can be found in Bugsnag settings dashboard, under organization and project settings.

  1. Add your Bugsnag personal auth token to the environment variables of your backstage backend server (you can find it in https://app.bugsnag.com/settings/{organizationaname}/my-account/auth-tokens), in the form of the word 'token' followed by your token. So it should look like this:

    BUGSNAG_PERSONAL_TOKEN="token <your-api-key>"

Links

  • Backstage
  • Get hosted, managed Backstage for your company: https://glint.io