heroku/umpire

Issues

• Implement StandardDB

  #66 opened 5 years ago by mmowris
  1

• Timeouts in the logs...

  #58 opened 6 years ago by jmervine
  3

• Umpire Playbook needed.

  #54 opened 6 years ago by jmervine
  4

• Log line missing status...

  #51 opened 6 years ago by jmervine
  1

• Smaller ranges (<300) don't consistently return results

  #40 opened 6 years ago by mikehale
  0

• query ranges < 300

  #42 opened 6 years ago by joshuatobin
  0

• Better documentation

  #43 opened 6 years ago by reidmix
  0

• composite metric queries should throw a 200 with missing metrics

  #46 opened 6 years ago by joshuatobin
  1

• Configure API keys as salted hashes

  #36 opened 6 years ago by jstangroome
  0

• log librato results

  #39 opened 6 years ago by jmervine
  2

• Compose functions and empty values have problems

  #21 opened 6 years ago by freeformz
  0

• Set User Agent to umpire / version and stuff

  #22 opened 6 years ago by freeformz
  0

• Better support incomplete data in latest Librato bucket

  #29 opened 6 years ago by nzoschke
  0

• Return links to metrics involved for errors

  #20 opened 6 years ago by freeformz
  0

• add median to the aggregation list.

  #37 opened 9 years ago by evanmcc
  1

• Undeclared dev dependency

  #28 opened 11 years ago by darkone23
  1

• Umpire doesn't respect graphite functions when using graphite style "{multiple,options}"

  #18 opened 12 years ago by XavM
  1

• Librato empty results exception

  #12 opened 12 years ago by nzoschke
  2

• Warning state

  #4 opened 12 years ago by mikehale
  1

• Consider *not* using HTTP return codes to indicate check status

  #5 opened 12 years ago by mikehale
  3

• more graceful handling of unreachable metrics service

  #3 opened 12 years ago by mmcgrana
  2

• revisit bamboo / cedar latency checks

  #2 opened 13 years ago by mmcgrana
  1