Hardware Observer
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 762 | 08 Jan 2026 | |
| latest/stable | 761 | 08 Jan 2026 | |
| latest/stable | 760 | 08 Jan 2026 | |
| latest/stable | 759 | 08 Jan 2026 | |
| latest/stable | 758 | 08 Jan 2026 | |
| latest/stable | 757 | 08 Jan 2026 | |
| latest/stable | 756 | 08 Jan 2026 | |
| latest/stable | 755 | 08 Jan 2026 | |
| latest/stable | 754 | 08 Jan 2026 | |
| latest/stable | 753 | 08 Jan 2026 | |
| latest/stable | 752 | 08 Jan 2026 | |
| latest/stable | 751 | 08 Jan 2026 | |
| latest/stable | 15 | 17 Jan 2025 | |
| latest/candidate | 762 | 11 Dec 2025 | |
| latest/candidate | 761 | 11 Dec 2025 | |
| latest/candidate | 760 | 11 Dec 2025 | |
| latest/candidate | 759 | 11 Dec 2025 | |
| latest/candidate | 758 | 11 Dec 2025 | |
| latest/candidate | 757 | 11 Dec 2025 | |
| latest/candidate | 756 | 11 Dec 2025 | |
| latest/candidate | 755 | 11 Dec 2025 | |
| latest/candidate | 754 | 11 Dec 2025 | |
| latest/candidate | 753 | 11 Dec 2025 | |
| latest/candidate | 752 | 11 Dec 2025 | |
| latest/candidate | 751 | 11 Dec 2025 | |
| latest/candidate | 15 | 02 Jan 2025 | |
| latest/edge | 774 | 22 Dec 2025 | |
| latest/edge | 773 | 22 Dec 2025 | |
| latest/edge | 772 | 22 Dec 2025 | |
| latest/edge | 771 | 22 Dec 2025 | |
| latest/edge | 770 | 22 Dec 2025 | |
| latest/edge | 769 | 22 Dec 2025 | |
| latest/edge | 768 | 22 Dec 2025 | |
| latest/edge | 767 | 22 Dec 2025 | |
| latest/edge | 766 | 22 Dec 2025 | |
| latest/edge | 765 | 22 Dec 2025 | |
| latest/edge | 764 | 22 Dec 2025 | |
| latest/edge | 763 | 22 Dec 2025 | |
| latest/edge | 15 | 03 Nov 2023 |
juju deploy hardware-observer
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Migrate from hw-health
The hw-health charm utilized the older (and deprecated) LMA(Logging, Monitoring and Aggregation) stack for monitoring and alerting.
To migrate the hw-health deployment to Hardware Observer, follow the these steps:
-
If you want to have the option to restore your current deployment later, back up your current deployment bundle:
juju export-bundle --filename old_model.yaml -
Remove the existing hw-health charm to avoid any potential incompatibility between the hw-health charm and Hardware Observer charm.
juju remove-application hw-health -
Deploy the
hardware-observerapplication, and relate it to the same principal charms hw-health used to be related to. If you’re not sure which are the correct principal applications, refer to the bundle exported in step 1.juju deploy hardware-observer juju relate hardware-observer <principal-charm> -
Follow the instructions on Integrate with COS page for instructions about how to propagate the metrics and alerts to the new monitoring system.
-
If you no longer need the legacy LMA stack components, remove them.
If you want to read more about migrating from an LMA based workload to COS-Lite, check the Migrating from LMA to COS-Lite guide.