Tags give the ability to mark specific points in history as being important
-
0.11.2
adf6f4dd · ·Improved content type handling and error handling Updated: - Add content-type to alert target definition and limit to text or JSON. - Add name to alert target definition as optional; will be pointed at URL if not provided. Name is printed in info message at startup. - No longer causes database warning on null value for previous state when a new status is registered
-
0.9.2
7a64364e · ·Improve status query performance New: - Split statii table into statii and statii_history, where statii now contains only the latest status reported by the node. This makes core status queries much simpler and faster. Fixed: - Error responses on some queries - Validate/cancel acknowledgement triggers on update as well as insert - Acknowledgement flag returned in status as well as the message to support acknowledgements without messages
-
0.9
6aedd6df · ·Attributes and API updates New: - Define attributes on nodes - Group nodes by attribute value - Go-based testing Changed: - Updated API route for all current statuses to `/` (so `/api/`) - Updated dashboard route to `/` - No longer using 'v' to prefix version - Removed agent to own repository
-
v0.4
9c2fbddf · ·Staleness checking - Agent can now report how long until next report can be expected - Server takes this an determines whether reports are stale - Dashboard client shows as faded if stale Also: - Dashboard client reveals when last report came in, in hover text - Configurable thresholds in `time-machine` check