Releases: exelban/JAM
Releases · exelban/JAM
v0.0.7
v0.0.6
- feat: added html/css/js minification before sending a file
- fix: fixed default success and failure threshold when not specified (SuccessThreshold=1, FailureThreshold=2)
- feat: added incident details with http status code and http response
- feat: added missing http code when server is unreachable (522/523/523) and by default 503
- feat: delete incident if it was less than 1 second
v0.0.5
- fix: fixed watcher error that causes sending alert on every check
- feat: added proper rest server url on start
v0.0.4
- fix: fixed not loading templates when debug is on but not in dev mode. This means that local templates are missing, and if local templates are missing the included ones must be used
- feat: added UI settings that allows to set web page title and hide url of the host if name is provided
- feat: initialized SMTP notifications
v0.0.3
v0.0.2
Bug fixes
- fix: fixed forever loop in template loader
- fix: removed omitting responses when a call is not ok (basically when the host could not be reached). It must not be omitted but marked as an unsuccess request
New features
- feat: hidden mongo url credentials
- feat: added incident history per host and enabled the last outage information for the host details
- feat: changed host id generation to make id more compact
- feat: removed default SuccessThreshold and FailureThreshold values. No values means that the success and failure threshold will be 1.
- feat: removed tags since now hosts could be grouped by group
v0.0.1
- feat: added description tooltip to the service header
- feat: added average response time chart generation and added it to the service details page
- feat: changed default storage backend from memory to boltdb. Removed storage type configuration from config file and moved to the app argument.
- feat: redesigned host page. Added information about SSL certificate, last outage