IoTaWatt VS Grafana

If anyone is interested in having this type of real-time usage data for their own own home, I highly recommend IoTaWatt: https://iotawatt.com

It's a completely local energy monitor that you can install into your home's circuit breaker panel, and then view dashboards or read data via an API from a local web server running on-device. You choose how many sensors you want, but you can monitor your whole home as well as individual circuits.

For example, I track and trigger automations when my various appliances (laundry, dishwasher, microwave, etc) start/stop. It's very cool. Just be warned that it does require some research, basic understanding of electricity, and comfort working with high voltage mains connections if you plan to DIY it but I found it approachable and easy to setup.

What it looks like: https://i.ibb.co/qBVmBD1/IMG-1595.jpg

I use an IotaWatt system. It's super easy to install and manage. It uses inductive sensors at your circuit breaker so you can see your total usage and per circuit usage. It also easily hooks into HomeAssistant but that's a bit more advanced of a project.

I have an IotaWatt and am pretty happy with it. It was not the cheapest option; but is simple, reliable, and local only which checked all my boxes. I did install it myself; BUT this involved opening up and poking around inside my breaker panel. AFAIK this is pretty much required for any per-circuit home power monitoring. Insert "The power inside your breaker panel can kill you instantly and painfully" warning. My panel is mounted on the wall (rather than inside); and I guess I could have put the clamps on the wires where the exit the panel. But it would have been much harder to identify circuits. Also it would probably be much messier.

For individual circuit energy monitoring, I use Iotawatt. This involves installing CT clamps in the main breaker panel to monitor the circuits you want to monitor. I’m comfortable doing it myself but if you’re not, DO NOT mess around with it, hire a professional electrician instead because you can get electrocuted.

IoTaWatt https://iotawatt.com

If you really want to mail down your sources of current draw, I can’t recommend this enough: http://iotawatt.com

Since you have home automation, you may already know of IoTAWatt - it's a little cheaper than others, and works really well on its own or with HomeAssistant etc.

Sense is really good at measuring overall usage. Their neural network analysis to identify individual devices is anything but reliable. If this is important to you, I suggest you monitor individual circuits with something else (eg. iotawatt).

Monitoring application logs is a crucial aspect of the software development and deployment lifecycle. In this post, we'll delve into the process of observing logs generated by Docker container applications operating within HashiCorp Nomad. With the aid of Grafana, Vector, and Loki, we'll explore effective strategies for log analysis and visualization, enhancing visibility and troubleshooting capabilities within your Nomad environment.

To help us visualize these scenarios, we'll build a Grafana Dashboard so we can follow along.

Visualization and Analysis: Choose a tool with intuitive and customizable dashboards, charts, and visualizations. A question to ask is, "Are the visualization features of this tool user-friendly and adaptable to our team's specific needs?" Tools like Grafana and Kibana provide powerful visualization capabilities.

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

Grafana

Yes I'm aware that Grafana is open source but the method I used to find the API endpoints is far quicker than digging through hundreds of files in a codebase I'm not familiar with.

So, you will add one last container to allow us to visualize this data: Grafana, an open-source analytics and visualization platform that allows us to see traces and metrics simply. You can set Grafana to read data from both Tempo and Prometheus by setting them as datastores with the following grafana.datasource.yaml config file:

In example above, we use 2 additional parameters: code (HTTP response code) and page (page identifier), which provide detailed statistics. For example, you can build such graphs in Grafana:

Robin switched to the Grafana dashboard tab, and sure enough, the 5xx volume on web service was rising. It had not hit the critical alert thresholds yet, but customers had already started noticing.