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

apollo-server-statsd

v0.0.26

Published

Apollo GraphQL server statsd middleware

Downloads

17

Readme

apollo-server-statsd

Installation

$ npm install apollo-server-statsd

send page views from you web app

app.use((req, res, next) => {
  metrics.send('pageview', 1, [`"client": "${_package.name}", "version": "${_package.version}", "page": "${req.path}"`]);
  next()
})

initialise metrics and start app monitor

const metrics = new _metrics({tags: [`"client": "${_package.name}", "version": "${_package.version}"`]});
metrics.startMonitor()

decorate schema middleware will report resolve time and resolver name + operation name

{ "requests": 1 ,"type": "server","page": "unknown","operation": "Menu"} { "response_time": 5.996299 ,"type": "server","page": "unknown","operation": "Menu"} { "resolve_time": 0.09399 ,"operation": "App","resolver": "session"}

{ "requests": 1 ,"type": "browser","page": "/sport/","operation": "Articles"} { "resolve_time": 0.076701 ,"operation": "Articles","resolver": "getArticles"}

const _schema = metrics.decorateSchema(schema);
app.use(
    '/graphql',
    metrics.graphqlStatsdMiddleware(),
    graphqlExpress(request => ({
      schema: _schema,
      context: {},
    }))
  )

module uses NATS as a message protocol it sends data to Telegraf agent which stores data into InfluxDB

than you can use Grafana to build nice dashboards

telegraf.conf

[[inputs.nats_consumer]]

    servers = ["nats://127.0.0.1:4222"]

    subjects = ["metrics"]

    queue_group = "metrics"

    name_override = "nats_metrics"

    data_format = "json"

    # tag_keys = [
    #   #host by default
    #   "client", # applicationName
    #   "version", # application version
    #   "instance", # 80, 8080 or 3000, 3001 (port)
    #   "type", # browser or server
    #   "page", # actual website page
    #   "operation", # can be graphql operationName or coma separated list of the operationNames or microservice arbitrary name
    #   "resolver", # resolver function name
    #   "error" # error
    # ]

    tag_keys = [
      "client",
      "version",
      "instance",
      "type",
      "page", 
      "operation",
      "resolver",
      "error" 
    ]