veyepar: Continuous Dashboarding

Author(s):	Christopher Biggs
Location	Plenary Hall
Date	jan Sun 15	Days Raw Files
Start	18:30	First Raw Start	18:07
Duration	0:30:0	Offset	0:22:49
End	19:00	Last Raw End	19:07
Chapters	00:00 0:05:12 0:26:31
Total cuts_time	27 min.

http://linux.conf.au/schedule/presentation/115/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Continuous_Dashboarding_your_devops_airbag.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

The concept of "Continuous Delivery" has been paraphrased as 
"Move fast and break things", that is automate your testing and deployment 
to remove as many delays as possible between developer and
production, and be prepared to react rapidly when something goes wrong.

The trick is knowing whether something has gone wrong.

Most businesses have analytics, monitoring and dashboards.  
In fact, if you look really hard, most businesses have a dozen or more 
different silos of monitoring data.   The problem is that it's difficult
to get a business-wide overview of all this data.

Node-RED is a visual data-flow tool that has a rich collection of 
interfaces to other services, and is capable of talking to most of these 
silos in order to provide synergistic insights, and real time alerts.

In combination with mobile dashboard tools like Blynk, this allows 
targeted mobile dashboard applications to be built and deployed in minutes, 
for one user or a thousand.

The attendee will learn the capabilities of Node-RED and Blynk, 
see some examples of dashboard apps, and receive practical advice on 
how to get started with their own data.

With "dashboard driven development" your process becomes first build 
a dashboard to monitor some element, second make a change, third
verify that the change had the desired effect.

Every time you make a change to your operating environment, you'll be 
able to monitor vital statistics from your pocket, in real time.

The collection of dashboards you've built over time will give you increased
confidence whenever you make a change that your business' key performance 
metrics are where you expect them to be.

Comment:

production notes