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

graphite-feeder

v0.0.9

Published

Fetch metrics from external sources and feed data to graphite.

Downloads

25

Readme

Graphite Feeder

Build Status Coverage Status Dependency Status devDependency Status

Docker build

Introduction

Feed metrics from several sources to graphite.

Installation

No node package deployed to npm yet. Please see section about development to build app yourself.

Configuration

node-config is used for managing configurations.

Configurations are stored in configuration files within your application, and can be overridden and extended by environment variables, command line parameters, or external sources.

Development

Setup docker container running graphite docker-graphite-statsd

sudo docker run -d \
  --name graphite \
  -p 80:80 \
  -p 2003:2003 \
  -p 8125:8125/udp \
  hopsoft/graphite-statsd

If you are developing on MacOS you need to have boot2docker installed and running to be able to use docker.

To access the graphite web UI go to http://localhost/

On MacOS you need to use the proper IP of the boot2docker container (boot2docker ip) instead.

Clone repo and change to directory

git clone [email protected]:commercetools/graphite-feeder.git graphite-feeder && cd $_

Create a configuration file config/local.yaml and adjust missing values.

# configuration for graphite/carbon
graphite:
  host: localhost # use boot2docker IP on MacOS
  port: 2003 # carbon port

# configuration for Salesforce feeder
salesforce:
  username: # required when feeding from Salesforce
  password: # required when feeding from Salesforce
  token: # required when feeding from Salesforce

Resolve and install required dependencies.

npm install

Build and run salesforce feeder (using DEBUG level for logging)

grunt && DEBUG=* ./bin/feeder-salesforce -d

Release npm package using the predefined grunt task.

grunt release

Docker

There is also a docker container for easy setup/execution of the CLI.

Run docker container:

docker run -v /path/to/config/:/config -e NODE_CONFIG_DIR=/config/ sphereio/graphite-feeder

Set an alias for repeated calls:

alias feeder='docker run -v /path/to/config/:/config -e NODE_CONFIG_DIR=/config/ sphereio/graphite-feeder'

After setting the alias you can simply use:

feeder

Feeders

Feeders are used for quering data from different sources and feeding the data into graphite. The following section describes the available feeders.

Salesforce

The Salesforce feeder queries data using Salesforce API and feeds the metric to graphite.

Sample configuration to push a metric to graphite. The configuration defines for each data you want to query a SOQL (Salesforce Object Query Language) as well as the mapping to resulting graphite metric.

# configuration for Salesforce feeder
salesforce:
  prefix: salesforce # prefix for graphite path
  datasources: # sources
    revenue: # query invoiced opportunities
      query: SELECT Account.name, Amount, CurrencyIsoCode,Type FROM Opportunity WHERE FiscalYear=2015 AND (StageName='Invoice' OR StageName='Receipt of payment')
      mapping: # configure mapping salesforce result -> graphite metric
        path: de.commercetools.opportunities.#{Account.Name}.#{Type}.amount.#{CurrencyIsoCode} # define path (field names from result allowed)
        value: Amount # value field in result
        timestamp: CloseDate # date field in result

You can define multiple data sources if you like to query and push different metrics from Salesforce to graphite.

# configuration for Salesforce feeder
salesforce:
  prefix: salesforce # prefix for graphite path
  datasources: #
    <key>: ...
    <key>: ...