With an ever-growing market of digital products, it is becoming increasingly important for every business to ensure a high level of customer satisfaction. In the past, companies might have been able to get away with slow or messy websites. Today, if a customer gets frustrated even once, they will likely abandon your product in search of a better replacement.

In today’s fast-paced IT ecosystem, agility and efficiency are not just goals but necessities. So why waste an hour (or more) manually onboarding individual devices when you can leverage the LogicMonitor API to automate the onboarding process for an entire site in just minutes from a simple CSV file? In this article, we’re going to review how LogicMonitor administrators can maximize efficiency and transform their IT operations using LogicMonitor’s REST API and Powershell.

Regression testing is not a new concept. However, historically, it has been limited to functional testing due to the setup, configuration, and maintenance required to simulate a production environment accurately. Many teams have found the cost outweighs the benefits, but with the advent of production traffic replication (PTR), it’s become a viable option to regression test performance, especially for those running applications in Kubernetes.

We are very excited to announce that we redesigned our monitoring results chart to make it easier for you to understand check performance over time and easily investigate any past anomaly. The redesign is a result of our UX research that showed that the old check overview chart made it challenging for users to find check results from the past. While we were redesigning our monitoring results charts, we wanted to achieve two things: And, we achieved this in three attempts. Let’s dive in.

I wish someone had told me that I shouldn’t hop between frameworks. Just like learning four programming languages in your first year, in my experience spending time content switching as a beginner is wasted effort. If I’d spent a solid year learning how to deploy services on AWS, then when it was time to learn Azure, I’d see more similarities than differences and find it a lot easier to pick up a second public cloud.

Friends of this blog know that I am a big fan of building internal tools, or as we call them, "tools that help scale people". As the name suggests, internal tools are used, well, internally and as such usually will require their access to be restricted to the company's staff and network. In the past, I've written about how to use Tailscale for authentication of internal tools using HTTP. In this post, I will show you how to use Tailscale for gRPC authentication in Golang.