---
title: Charmhub | Deploy Hardware Observer using Charmhub - The Open Operator Collection
description: Deploy the latest version of Hardware Observer on any cloud.
url: https://charmhub.io/hardware-observer/docs/migrate-from-hw-health
---

# Hardware Observer

[Canonical BootStack Charmers](https://charmhub.io/publisher/bootstack-charmers "View all packages from Canonical BootStack Charmers")

* [Canonical BootStack Charmers](https://charmhub.io/publisher/bootstack-charmers "View all packages from Canonical BootStack Charmers")

Platform:

26.04

24.04

22.04

20.04

18.04

stable 894

```
juju deploy hardware-observer
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Relevant links

* [Homepage](https://github.com/canonical/hardware-observer-operator)

---

#### Contacts

* [Submit a bug](https://github.com/canonical/hardware-observer-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

# Migrate from hw-health

The [hw-health charm](https://charmhub.io/hw-health) 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](https://charmhub.io/hardware-observer/docs/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](https://discourse.charmhub.io/t/migrating-from-lma-to-cos-lite/11998) guide.

---