hardware-observer

Hardware Observer

  • Canonical BootStack Charmers
Channel Revision Published Runs on
latest/stable 154 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/stable 15 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/stable 119 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/stable 155 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/stable 118 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 154 14 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 155 14 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 15 02 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 119 02 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 118 02 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 157 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 156 17 Jan 2025
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 119 11 Nov 2024
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 118 11 Nov 2024
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 15 03 Nov 2023
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
juju deploy hardware-observer
Show information

Platform:

Ubuntu
24.04 22.04 20.04 18.04

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:

  1. 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
    
  2. 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
    
  3. 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>
    
  4. Follow the instructions on Integrate with COS page for instructions about how to propagate the metrics and alerts to the new monitoring system.

  5. 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.


Help improve this document in the forum (guidelines). Last updated 10 months ago.