Monitoring NodeFly’s White Board vs. Monitoring with NodeFly’s Dashboard

The NodeFly HQ sits on the edge of Gastown, a historic slice of downtown Vancouver that blends tourist destinations, restaurants, professional offices, acting and film schools, tech and new media start-ups, and various pubs. And the office whiteboard sits at the edge of NodeFly’s Gastown HQ. 


The whiteboard is actually a white wall covered in dry erase paint from floor to ceiling. It is a focal point within the office, displaying an eclectic combination of scribbles, growth plans, important dates, task lists, inspirational quotes, sketches, and goofiness.

Here are a few of things that have appeared on the NodeFly whiteboard board:

  • A reminder to have the NodeFly code as the first require before any modules. We want our users to be able to see data, and if the code is anywhere else that data may not be visible.
  • A Mike Tyson quotation, stating “Everyone has a plan until they get punched in the mouth.” Because it is true, though we don’t intend to get punched in the mouth to re-affirm it.
  • A drawing of Endpoint Paths Visualization. We’ve been very happy to add dependencies to our dashboard. Read more about that capability in an earlier blog post,  “Monitor your Node.js with NodeFly and Endpoint Paths Visualization.”
  • An enigmatic reference to Богдан друїдів. There is really no explaining that one.
  • Dates for NodePDX, GlueCon, Node in the Wild, Velocity and WebPerfDays. We are looking forward to meeting our users and other fans of Node.js at some of these events, and are still nailing down the ones that fit into our schedule best. We’re definitely going to be at GlueCon on May 22-23.
  • An arrow directing the words “This is where the magic happens!” into a sun-like orb.
  • A map of our dashboard graphs, with existing versions and planned updates.

Subject matter on the board becomes irrelevant quite regularly. A particular date or milestone passes, plans change, a graphic no longer interests us, or a specific option we jotted down no longer fits. We erase it to create new empty spaces, and those empty spaces soon fill up again. And the cycle continues.

The cycle continues. Where have we heard this before? Oh yes, the NodeFly Monitoring Loop – which is also on the wall.  “Monitor. Profile. Fix. Release.”

We have spoken before about the monitoring loop, and how we think your best approach to creating a Node.js product is to monitor it from the start. Our wall can be seen as an analogy for this Node.js monitoring.

Projects start and finish on the board, and thanks to additional scribbles and sketches we get to observe progress each step of the way. You also get to observe progress via the NodeFly dashboard, ideally watching your Node.js product from start to finish.

We tweak the board the way you would tweak your Node.js code, updating and adjusting to improve and enhance the details.

The whiteboard, and the NodeFly dashboard, provides a visibility to see what is happening so we can adjust and update things so they work out as effectively as possible. By seeing things in front of us, we are shown both the finer details and the big picture to make changes.

“Know what happens in real-time,” says another piece of our board. That’s true of the board, and of the NodeFly dashboard. 

(And, as always, you can access the dashboard via our site at )