Security should be top of mind these days. I wrote an article years ago about three lessons you can learn from doing a network security analysis. Taking the appropriate steps is even more crucial now than then.
But how do you protect your organization when you need to help troubleshoot an application problem and need to capture packets? In this post, let’s talk about how you can go about doing that.
Note: This post was originally written for the Scalyr blog. You can check out the original here.
Some things aren’t always what they seem.
You’re tasked with engineering a solution that your organization needs. You implement it with a tool that seems relatively easy to set up. But over time, you realize that there’s no Easy button.
Elasticsearch is an example of one of those things. It’s a great product for collecting event data fairly quickly and easily. You start with one data node in one cluster and go from there. And because it’s free and open-source (for now), it’s even better. But as your Elasticsearch cluster grows and collects more data, you start to have some scaling issues. In this post, I’m going to provide some information on scaling an Elasticsearch implementation, as well as some general recommendations for proactive ways to scale Elasticsearch.
You just got a call about an application slowness issue. You’ve been told that it’s not an application issue and that it must be somewhere on the network.
When you need to capture some data, for whatever reason, one question that inevitably comes up is where you should capture. What’s the best location for a packet capture? That’s a good question to ask yourself.
If you don’t, you should be. So let’s talk about that now.
In this post, you’ll learn what SNMP is and some challenges you may have when using it to monitor your infrastructure. You’ll also learn some best practices you should consider when implementing SNMP monitoring.
Gartner predicts that public cloud revenue will increase by 17% in 2020. The biggest percentage increase is expected with IaaS.
So you’re clearly not alone.
But what’s the plan after the move for making sure your applications and infrastructure perform at expected levels in the cloud?
When you no longer have full control of your infrastructure, monitoring becomes even more important than it did on-premise. Unfortunately, it seems some companies get the impression that moving to the cloud will solve all their issues.
The cloud has many benefits, but not having to monitor your workloads isn’t one of them. I want to show you why, and provide some tips for cloud performance monitoring.
But Gartner’s 2018 hype cycle did have cloud migration falling into the “trough of disillusionment.” This could be because migrating data to the cloud isn’t easy. Organizations encounter numerous issues when trying to take advantage of the cloud’s benefits.
Organizations need to plan properly before undertaking such an endeavor. Let’s look at what you can do to minimize the issues that can plague a cloud data migration project.
New Relic APM helps you to understand the performance of your applications. I wanted to run some performance tests with it for my review. In this video, I walk through the installation process. Here it is….
I was recently asked by APMdigest, a community blog in the Application Performance Management space, to provide any APM predictions for 2020. Along with other analysts, consultants, and vendors, my prediction was published recently in APMdigest’s 10th annual predictions list. This year, I provided one prediction about page load time.
As for me, the gist of what I predict is that page load time will become even more important in 2020 than it is now. In this article, I wanted to go into a little more detail about why I made this prediction.
Competition is a funny thing. To gain or keep an edge against your
competitors, you may need to push the envelope to use newer technologies
and processes. But done wrong, that very technology or process could
lead to your ruin.
This is where we are with DevOps. The methodology that became popular in the mid-to-late 2000s is embraced by many companies . Done the right way, it will help your organization challenge its competition to keep up with customer and user demands. But done incorrectly, it could lead to more challenges, leading to degraded user experience and product performance. To mitigate these challenges, your organization needs to include application performance monitoring (APM) as part of its DevOps implementation.