influxdb/notification
Johnny Steenbergen 300d89887d chore(kv): refactor notification endpoint to use reusable uniqByNameStore
this is work moving us towards more reusable components that add some
rigidity around handling indexes and the entity bucket. The behavior
is very common across much of the kv pkg. This can be reused throughout.
adding some easy wins for tracing(eventually metrics) that enable more
insight that what is currently possible. It normalizes these concerns
across the kv store.
2019-12-30 16:44:57 -08:00
..
check fix: add custom marshaler to dashboard builder config to stop breaking all external api clients with nil vals 2019-12-26 14:53:14 -08:00
endpoint chore(kv): refactor notification endpoint to use reusable uniqByNameStore 2019-12-30 16:44:57 -08:00
flux fix(notification/check): range outside logic 2019-09-09 15:11:08 -04:00
rule feat(pkger): add application functionality for the notification rules resource 2019-12-20 12:48:46 -08:00
duration.go chore: refactor bits of checks and its dependencies for readability 2019-12-18 11:07:19 -08:00
status.go fix(notification): fix the any checkLevel string 2019-09-05 15:11:43 -04:00
status_test.go Add Any to rule levels (#14866) 2019-08-29 17:46:00 -07:00
tag.go feat(influxdb): add predicate package 2019-10-18 12:02:52 -04:00