Download graphs from Graphite and upload them to HipChat
Last updated 6 years ago by nmaclennan .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install hubot-chartroom 
SYNC missed versions from official npm registry.

Hubot Chart Room

Give your Hubot its own room for piles of Graphite graphs

Build Status Code Climate Code Coverage

Downloads Version License

Why not just use hubot-graphite

Actually, you should use hubot-graphite if you can. That has support for saved graphs and is significantly faster to respond.

However, the reason it is significantly faster to respond, is because the majority of what it does is construct a URL for the graph.

This is great if your Graphite is accessible from outside of the LAN, so HipChat can generate a thumbnail and all users in the room can get to the graph. But what makes ChartRoom different is that this actually downloads the image from Graphite and shares it via the HipChat API.

NOTE: This script needs a single preconfigured room to share this image with. However once it is posted, Hubot finds the S3 URL and shares that with the requesting user or room.

This extra step of uploading it to a specific room first is to get around issues with the hubot-hipchat adapter regarding renaming rooms. If a room has been renamed, Hubot will be unable to locate the API ID of the room and so will be unable to share that image directly to the room. So users are just expected to provide an API ID for a room in the environment variables. Images will be shared there first, before their links are copied to the end user/room.

Do I need to use to HipChat adapter?

Well...kind of. Mostly. All of the actual messaging stuff it does is adapter independent. But it uses the HipChat API to get the images up onto the Internet first, then to find the S3 URL for the images. Everything other than that is adapter independent.

So you could, in theory, use any adapter you wanted, as long as you also had valid HipChat API information.


Install the package from npm

$ npm install hubot-chartroom --save

Then edit your external-scripts.json to include the package



GRAPHITE_SERVER: the hostname/ip of your graphite server.

GRAPH_ROOM_ID: the API ID of a HipChat room to which all graphs will be initially shared:

  • This should be a "service room" without anyone else in it (unless they just want to see random graphs).
  • To get the API ID, log into your account on, go to the room list then click on your room to find it.
  • As I say elsewhere, this is just where graphs get uploaded, they eventually end up shared with the right room/user.

HIPCHAT_TOKEN: an API token for your hubot can use for uploading to hipchat.

  • You need to log into as your hubot, click Edit Profile, then click API to generate your token.


SUCCESS_MESSAGE: What hubot says after it has completed a message. Defaults to (yougotitdude)


The user saves and requests a graph...

[Room: warroom]
<Norm> hubot save graph jenkinscpu as target=collectd.jenkins001.CPU.load
<Hubot> You can now use "graph me jenkinscpu" to see this graph.
<Norm> hubot graph me jenkinscpu
<Hubot> (yougotitdude) Fetching graph and uploading to HipChat...

Hubot fetches the graph from Graphite and uploads it to the configured room...

[Room: hubot_graphs]
<Hubot> upload.png 539bdb5b-9ff4-2e7d-8cfa-5f889c50645b

Hubot finds the URL of the file in the message containing the above GUID and posts it to the requesting room/user

[Room: warroom]

Current Tags

  • 1.3.1                                ...           latest (6 years ago)

8 Versions

  • 1.3.1                                ...           6 years ago
  • 1.2.2-0                                ...           6 years ago
  • 1.2.1                                ...           6 years ago
  • 1.2.0                                ...           6 years ago
  • 1.1.0                                ...           6 years ago
  • 1.0.3                                ...           6 years ago
  • 1.0.1                                ...           6 years ago
  • 1.0.0                                ...           6 years ago
Maintainers (1)
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (2)
Dev Dependencies (11)
Dependents (2)

Copyright 2014 - 2016 © |