Skip to content

Releases: laitco/tailscale-healthcheck

1.3.1

08 Oct 19:09

Choose a tag to compare

Full Changelog: 1.3.0...1.3.1

1.3.0

29 Aug 19:53

Choose a tag to compare

Full Changelog: 1.2.6.1...1.3.0

Version 1.2.6.1

22 Jul 18:59

Choose a tag to compare

Fixed: Support for ISO 8601 timestamps with fractional seconds from Tailscale API using dateutil.parser.
Added: python-dateutil to requirements for robust timestamp parsing.

Fixes Issue #19 reported by @HackerJL. Thank you!

Version 1.2.6

14 Apr 20:28

Choose a tag to compare

New Features as mentioned in #16 [Feature: Output configured values]

Added capability to display settings:
New DISPLAY_SETTINGS_IN_OUTPUT environment variable (default: NO)
Optional display of all configuration settings in API output
Secure masking of sensitive credentials (AUTH_TOKEN, OAUTH_CLIENT_SECRET)
Default configuration values shown when settings are empty

Version 1.2.5

14 Apr 18:26

Choose a tag to compare

New Features as mentioned in #15 [Feature: Implement client_version_health]

Added tag filtering capabilities:
Tag filters (INCLUDE_TAGS, EXCLUDE_TAGS)
Support for wildcard patterns in filter strings
Include filters take precedence over exclude filters
Multiple tag matching support per device

Version 1.2.4

14 Apr 08:27

Choose a tag to compare

New Features as mentioned in #14 [Add filter by ACL tags with wildcard support for include/exclude]

Added tag filtering capabilities:
Tag filters (INCLUDE_TAGS, EXCLUDE_TAGS)
Support for wildcard patterns in filter strings
Include filters take precedence over exclude filters
Multiple tag matching support per device

Version 1.2.3

14 Apr 00:45

Choose a tag to compare

New Features as mentioned in #9 [Feature: Add exclude and include Device filtering options]

Added device filtering capabilities:
Operating system filters (INCLUDE_OS, EXCLUDE_OS)
Device identifier filters (INCLUDE_IDENTIFIER, EXCLUDE_IDENTIFIER)
Support for wildcard patterns in filter strings
Include filters take precedence over exclude filters

Version 1.2.2

13 Apr 21:05

Choose a tag to compare

New Feature as mentioned in #4 [Feature: Add key_days_to_expire to output]

Added key_days_to_expire field showing the number of days until a device's key expires
Set to null when key expiry is disabled

Version 1.2.1

13 Apr 20:26

Choose a tag to compare

New Feature as mentioned in #3 [Feature: Add counters and global health parameters with threshold]

Added global health metrics with configurable thresholds
GLOBAL_HEALTHY_THRESHOLD (default: 100)
GLOBAL_ONLINE_HEALTHY_THRESHOLD (default: 100)
GLOBAL_KEY_HEALTHY_THRESHOLD (default: 100)
Added detailed counter metrics for monitoring device states
Healthy/unhealthy device counters
Online/offline device counters
Valid/expired key counters

Version 1.2.0

13 Apr 18:36

Choose a tag to compare

New Feature as mentioned in #2 [Add key expiery and build a combined health status]

Added key expiry monitoring with configurable threshold (KEY_THRESHOLD_MINUTES, default: 1440)
Introduced combined health status based on online status and key expiry
Added new health indicators in API response:
online_healthy: Device online status
key_healthy: Key expiry status
healthy: Combined status (true only if both checks pass)
Added keyExpiryDisabled and keyExpiryTimestamp fields in API response
Improved timezone handling for all timestamp fields