[//]: # (werk v2)
# ups_test: Handle unknown time since last test
key | value
---------- | ---
date | 2024-06-17T05:43:13+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The time since the last battery test is calculated via the difference between the current uptime and the uptime when the test was initiated.
This means the time cannot be determined if the uptime of the test initiation is larger than the current uptime.
Before, this lead to a
```
ValueError: Cannot render negative timespan
```
Now, the check will become UNKNOWN instead.
[//]: # (werk v2)
# ups_test: Handle unknown time since last test
key | value
---------- | ---
date | 2024-06-17T05:43:13+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The time since the last battery test is calculated via the difference between the current uptime and the uptime when the test was initiated.
This means the time cannot be determined if the uptime of the test initiation is larger than the current uptime.
Before, this lead to a
```
ValueError: Cannot render negative timespan
```
Now, the check will become UNKNOWN instead.
[//]: # (werk v2)
# Synthetic monitoring: Tests with status NOT RUN, SKIP or NOT SET go stale
key | value
---------- | ---
date | 2024-06-07T14:34:03+00:00
version | 2.4.0b1
class | fix
edition | cee
component | checks
level | 1
compatible | no
The test services become stale if the test status is NOT SET, NOT RUN, or SKIP.
Previously, tests with any of these statuses would go to the WARN state.
As a result of this werk, test services may change state and more the number of stale services may increase.
[//]: # (werk v2)
# Test notifications: Match host and service level
key | value
---------- | ---
date | 2024-06-17T09:54:41+00:00
version | 2.3.0p7
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
Even if configured, host and service level did not match while testing
notifications.
This has been fixed.
[//]: # (werk v2)
# sql: Allow macros in 'Query or SQL statement' field
key | value
---------- | ---
date | 2024-06-13T15:56:27+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
With the version 2.3, the usage of macros in the `Query or SQL statementw` field of
the `Check SQL database` was disallowed. With this Werk, it's allowed again.
[//]: # (werk v2)
# Rest API: Improvement of response data types
key | value
---------- | ---
date | 2024-06-13T14:07:51+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
In order to improvide the Rest API, adjustments have been made to the
data types returned in the `comments` and `downtimes` endpoints as
specified below:
* `Show a comment` and `Show comments` endpoints:
`entry_time` now shows the date stamp in ISO 8601 format.
Before: "Jun 03 2024 06:05:41"
Now: "2024-03-06T06:05:41+00:00"
* `Show downtime` and `Show all schedulled downtimes`.
`recurring` and `is_service` fields now are boolean types.
Before:
`recurring`: "yes"
`is_service`: "no"
Now:
`recurring`: true
`is_service`: false
[//]: # (werk v2)
# Test notifications: Match host and service level
key | value
---------- | ---
date | 2024-06-17T09:54:41+00:00
version | 2.4.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
Even if configured, host and service level did not match while testing
notifications.
This has been fixed.