It's often said that your network is the "backbone" of your IT infrastructure, underlying every other part of your enterprise IT. If your Cisco network infrastructure goes down or is experiencing performance issues, it's crucial that you have a real-time solution to identify and resolve the problem as soon as possible. But what does such a solution look like when it comes to Cisco networks?
In today’s post, we’ll dive into how we, at AppSignal, solved a daunting engineering challenge. Giving you a look into the kitchen, this post will show you how we tested a new database in production without having to worry about errors/downtime. Alright, let’s get cooking!
One of the major concerns when moving to the cloud is how to approach AWS S3 security. Companies may have moved their workflows to Amazon, but are still cautious about moving their data warehouse. And that is totally understandable. We have all heard about data breaches in companies like Facebook, GoDaddy, and Pocket. It’s important that access to information is done properly, in a limited and controlled fashion, to avoid such breaches.
As part of my job as a Senior Solutions Engineer here at Grafana Labs, I tend to pretty easily find ways out of technical troubles. However, I was recently having some Wi-Fi issues at home and needed to do some troubleshooting. My experience changed my whole opinion on logs, and I wanted to share my story in hopes that I could open up some other people’s eyes as well. (I originally posted a version of this story on my personal blog in January.) First, some background info.
Running and troubleshooting production services requires deep visibility into your applications and infrastructure. Virtual machines running on Google Compute Engine (GCE) provide some system logs and metrics without any configuration required, but capturing application and advanced system data has required the installation of both a metrics agent and a logging agent.
IT teams across the digital world are currently facing their biggest test yet. Ensuring that things are running smoothly when employees are working from home. And they’re doing a very good job at it. But, there’s always room for improvement right? If you’ve ever been a part of an IT team, you know the pain of jumping between multiple software tools, the effects of a broken down collaboration system and the struggle for visibility amongst team members.
On one of our monthly check-in calls, the Director of Infrastructure and Operations at one of our largest customers, was telling me how the one big problem he was still trying to solve is optimizing their OPEX or at least make it more predictable. He cited a popular Content Delivery Network (CDN) that they spend millions with as an example. The company had launched a new service and he spoke about how the CDN cost had quadrupled.
There are more than eight hundred pages of documentation for Pandora FMS. The science – and art, I think – of monitoring is very extensive. The needs of a large company are different from those of a medium or small organization. But even two large companies are not the same and their needs may be totally different.
