Skip to content

Latest commit

 

History

History
93 lines (79 loc) · 3.1 KB

CHANGELOG.md

File metadata and controls

93 lines (79 loc) · 3.1 KB

0.1.0

  • Implement sumo (name)
  • Implement lobotomize sumo
  • Chart support
    • Pie
    • StackedBar
    • counter
    • timecounter
    • lines
  • Old Todo
    • Implement some highchart adapters depending of widget
    • Add Hubot hear for this dev
    • Test on a true slack
    • Graph can be built on highchart or svg template
      • Split how work graph builder for allowing multiple implementation
      • Base on graph type
    • Use promises !
      • Break callback hell into promise composition
    • Clean generated image file
      • Auto find tmp file
      • Use it
    • Style graph
    • Learn hubot to learn
      • Learn from a json file (brain used)
      • Allow to erase memory via a command
    • Clean && Tidy && Refactor if needed
      • Clean todo's
      • SendToSlack (ensure work for common cases)
    • Package it !
      • Boulangerie repo
      • Readme
      • Npm publish
    • When hubot has learn return a message
    • Repository part 2
      • Add changelog
      • Issues followings subjects
      • Millestone them ?

Learn hubot to learn

POC on fact hubot can get a json file through slack Can be a link to file but it's less safer Finally we can brainwash hubot if we want ! Maybe if sumologic fix their API we could use it properly and avoid a lot of this stuff

Edit

Some of this feature have already been done. But this part of this package could improved a bit more

  • [] Erase brain should be possible only by some users
  • [] Should list all widget available...
  • [] Should add/update/remove unitary by a command

Learn hubot to make graphs with query

Instead of using dashboard data, use true results from a custom query. The naive way should to transform query results into dashboard data format. Like this graphs implementation should work as expected without no update on it.

We should use the same hubot command, but hubot have to warn user the result could not come as quickly as a widget result

  • Associate a query with a name and a graph type
  • Implement logic to transform sumo data into something usable for graph
  • Add hubot behavior
  • (Depending of : Learn hubot to learn) Update or consider it

Learn hubot to make beautiful graphs

  • Missing infos
    • Time range of current graph
  • Missing graph
    • Donuts
    • Text percentage
    • Filled line chart
  • Upgrade logic behind how we format rawData from sumo (to dumb for now)
  • Style should be configurable
  • Apply Color rules on some of them when sumo will give us that details

Learn hubot to let rocks for find his mistakes !

  • Implement a true logger to see what hubot do

Improve filesystem management

Instead of using promise of folder, use it or flag, this could avoid problem with promise. Other solution should be to create it at module install

  • Spec it :)

Other points

  • Find a way to delete what hubot send to slack
  • Make this part of hubot more customisable via brain of something (theme ?)