Hardware Observer
- Canonical BootStack Charmers
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 84 | 02 Jul 2024 | |
latest/stable | 13 | 01 Nov 2023 | |
latest/candidate | 113 | 15 Oct 2024 | |
latest/candidate | 112 | 15 Oct 2024 | |
latest/candidate | 13 | 30 Oct 2023 | |
latest/edge | 121 | 11 Nov 2024 | |
latest/edge | 120 | 11 Nov 2024 | |
latest/edge | 119 | 11 Nov 2024 | |
latest/edge | 118 | 11 Nov 2024 | |
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-observer
application, 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.