MagicMirror VS prometheus

I use MagicMirror to do this. It's a great piece of software. I'm a bit shocked nobody has mentioned this yet. https://magicmirror.builders/

The most used solution it’s https://magicmirror.builders/

I’m planning on using MagicMirror (https://magicmirror.builders/) to do this in my kitchen but without the mirror part (just a TV mounted in a niche on the wall). Did you build your software from scratch?

Check out Magic Mirror. Could be what you're looking for. https://github.com/MichMich/MagicMirror

Would this work with magic mirror?

https://magicmirror.builders/

If so I will order right away

Have a look at the Magic Mirror project https://magicmirror.builders/

You could also look into something like MagicMirror. not sure if you have a server to host, or looking for just local on iPad.

The final option seems to be basically homebrewing a solution using a program like MagicMirror and local image files installed on the pi. There quite a few guides out there on different ways to do this. But

You can still participate in distributed computing projects, just check out Science United which is one that uses BOINC for the project management. I've got it running on my Raspberry Pi (which primarily runs Magic Mirror so its nice to let somebody else get some benefit since its primarily a relatively static display). Also, Folding@Home did do some of the research into COVID, so it is staying up to date.

WriteRequest::timeseries is a vector (https://github.com/prometheus/prometheus/blob/main/prompb/re...) and

Developers widely use Prometheus as a system for operational monitoring and alerting for their projects. Here is a list of tools for monitoring frontend services with Prometheus.

Just to give an example of the power of Go for CLI builds, you may have already used or at least heard of Docker, Kubernetes, Prometheus, Terraform, but what do they all have in common? They all have a large part of their usability via CLI and are developed in Go 🐿.

Distributed system administrators need mechanisms and tools for monitoring individual nodes in order to analyze the system and promptly detect anomalies. Developers also need effective mechanisms for analyzing, diagnosing issues, and identifying bugs in protocol implementations. Logging, tracing, and collecting metrics are common observability techniques to allow monitoring and obtaining diagnostic information from the system; most of the explored code bases use these techniques. OpenTelemetry and Prometheus are popular open-source monitoring solutions, which are used in many of the explored code bases.

Setting up monitoring for a system, especially one involving GRPC communication, provides crucial visibility into its operations. In this guide, we walked through the steps to instrument both a GRPC server and client with Prometheus metrics, exposed those metrics via an HTTP endpoint, and visualized them using Grafana. The Docker-Compose setup simplified the deployment of both Prometheus and Grafana, ensuring a streamlined process.

Alerting and Notification: Select a tool with flexible alerting mechanisms to proactively detect anomalies or deviations from defined thresholds. Consider asking questions like "Does this tool offer customizable alerting options and support notification channels that suit our team's communication preferences?" A tool like Prometheus provides robust alerting capabilities.

Prometheus

Prometheus is an open-source monitoring and alerting toolkit. It is designed to monitor highly dynamic containerized systems, making it an excellent choice for monitoring Docker containers and Kubernetes clusters.

wget https://github.com/prometheus/prometheus/releases/download/v2.46.0/prometheus-2.46.0.linux-amd64.tar.gz

Prometheus: Open-source monitoring system. Often used together with Grafana.