~/talk

Jim Nichols, EnerNOC | Splunk .conf2014

links:none on file
slides:none on file

EnerNOC runs 30,000 energy sensors and builds a cloud-based demand response system that ingests meter data from every 5 minutes down to 2 seconds and must aggregate and report back to grid operators within 5-second latency. The stack mixes Exadata/Oracle with Hadoop/HBase and MongoDB on AWS, and Splunk provides operational visibility and dashboards that pay for themselves manyfold, spawn a new production-ops role, and now require Splunk high-availability and search-head clustering.

AI-written summary · about

  1. 0:00Introduction and welcome
  2. 1:04About EnerNOC and energy intelligence
  3. 2:28Customer use cases and ROI
  4. 6:58Analytics and technology stack
  5. 9:45Old vs new world data approaches
  6. 11:32Splunk’s role in operations
  7. 14:22Licensing and trial experience
  8. 15:05DevOps and Splunk at EnerNOC
  9. 18:58Empowerment through data access
  10. 21:45Splunk’s future needs and Q&A
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.