Hardware Observer

  • Canonical BootStack Charmers
Channel Revision Published Runs on
latest/stable 84 02 Jul 2024
Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/stable 13 01 Nov 2023
Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 113 15 Oct 2024
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 112 15 Oct 2024
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/candidate 13 30 Oct 2023
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 125 19 Nov 2024
Ubuntu 24.04 Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04
latest/edge 124 19 Nov 2024
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

Integrate with COS

Prerequisites

Bootstrap a juju controller on a microk8s cloud. Steps can be found in this guide.

Note: This is a separate controller from the one managing the Hardware Observer charm. We plan to build a cross model integration here.

Deploy COS-Lite

Follow these steps to set up cos-lite on microk8s: Deploy cos-lite on microk8s

Ensure to set up cos-lite with this offers overlay so that the COS model is ready for cross model relations. Relevant section in the above guide here.

Deploy Grafana-Agent

Deploy the grafana-agent machine charm in the same model as Hardware Observer. This will be used for scraping the prometheus metrics and exporting them to Prometheus in the COS model via cross-model-relations.

For more information on the usage of grafana-agent machine charm, see here.

# switch from microk8s model to the Hardware Observer one

juju switch other-controller:hw-obs-model

juju deploy grafana-agent

juju relate hardware-observer:cos-agent grafana-agent:cos-agent

Verify if the status of juju units is expected:

  • hardware-observer should in active status, if all the required resources/configurations are been provided.
  • grafana-agent should in blocked status because the required juju integration haven’t been provided.

The required integration can be provided by the juju offers. Verify if the offers from the COS model are visible.

# verify if offers are present

juju find-offers -m microk8s-controller:cos-model

Then add the necessary relations with the grafana-agent charm.

# add cross-model relations

juju relate grafana-agent cos.prometheus-receive-remote-write

juju relate grafana-agent cos.grafana-dashboards

juju relate grafana-agent cos.loki-logging

Now the architecture looks like below:

Check the dashboard

As described in this section of the COS docs, you can navigate to the dashboards for Prometheus and Grafana, and verify whether the metrics and alert rules from Hardware Observer are present.

Hardware Observer currently provides the following dashboards:

  • Smartctl Dashboard
  • BMC Dashboard

The Smartctl Dashboard displays metrics exported by the smartctl exporter. If the observed device supports the smartctl exporter, this dashboard will present all S.M.A.R.T. metrics collected.

The BMC Dashboard offers a comprehensive list of all System Event Log (SEL) records and ipmiseld status logs.


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