Operations | Monitoring | ITSM | DevOps | Cloud

Dashboard Fridays: Sample VMware dashboard

These three VMware dashboards built in SquaredUp provide a full overview of the data in a VMware deployment so users can spot performance issues and fix them fast. Having all the VM performance and health metrics in one place – for your VMs, VM hosts, and guest VMs – allows engineers to pre-empt issues and fix them before they become problems for end users.

Metrics vs. Logs vs. Traces (vs. Profiles)

In software observability, we often talk about three signal types - metrics, logs, and distributed traces. More recently I've been hearing about profiles as another signal type. In this article I will explain the different observability signals and when to use them in a clear and concise way.

Instrumenting Node.js code with Prometheus custom metrics

Automatic instrumentation is great, but to get the most out of your monitoring you often need to instrument your code. In this article I am going to explain how to instrument a Node.js express app with custom metrics using the Prometheus prom-client package. Although this article specifically addresses Node.js and express, my hope is that the general concepts are applicable to other languages too.

Dashboard Fridays: Sample Jira Dashboard

These Jira dashboards give a clear overview of your Jira instance and provide more details on the key items over which the engineering team needs oversight, like build status, critical bugs, and costs. Creating Jira dashboards in SquaredUp means Engineering Management doesn’t have the additional work of collating all the detailed Jira data to make sense of it from a high level. It also enables Release Teams to more easily consume data surfaced from all the engineering teams, while still being able to drill into the details of each dashboard as needed.