Operations | Monitoring | ITSM | DevOps | Cloud

Software teams are under increasing pressure to ship code faster than ever before, but without the right workflow and tools in place, this can introduce unnecessary risk and headache. We wanted to share how to configure deployments, identify issues, and track performance gains using tools and process to get the best results and enable you to ship software with speed and confidence. The tools we will be using in today’s example include Jenkins, Octopus, and Raygun.

We know from experience that many online businesses and website owners spend a lot of time and money on online marketing and getting conversions. However, sometimes, teams lose sight of one of the most basic of concerns, website uptime. Teams forget the impact of downtime, and they neglect to monitor their website’s uptime. As a result, when a website outage occurs—and it will—the downtime goes unnoticed, but the outage still affects visitors and potential customers.

Welcome to the new world, my friends. Now that working from home is our new reality, we've found that many of our customers are taking a much closer look at the technology that binds us all together and allows us to access corporate resources: the humble VPN. In the spirit of enablement, I’ve put together a quick list of dashboards that can help add that extra bit of visibility for our faithful Splunk Enterprise Security customers.

SOLID is one of the most popular sets of design principles in object-oriented software development. All of them are broadly used and worth knowing. But in this first post of my series about the SOLID principles, I will focus on the first one: the Single Responsibility Principle.

The current days of remote work and “IT Ops from home” may or may not be here to stay, but they definitely reinforce the need for consolidating and modernizing our monitoring. The challenges which multiple siloed tools create for understanding the big picture are only exacerbated by having just one screen to look at when monitoring our IT from our kitchen table.

If you thought the fishmonger’s hair net was the only kind of net you’re wrong. From Pandora FMS we will show you some more, so that you do not get lost without them. The term “network” is used in computing to name a set of computers connected to each other in such a way that they can share resources, services, and information. There are several ways to classify these networks, based on their scope, relationship, or connection method.

When discussing monitoring with IT and technical operations teams, it comes as no surprise that every team has its own parameters and requirements for their particular environment. Some teams just need an up-down of specific devices or interfaces, and others need more granular metrics like JVM or database performance. At the end of the day though, everyone is responsible for a service.

Consider for a moment which fundamental pieces of technology enable the modern web. Odds are, you’re thinking about things like Javascript and HTTP—and yes, they are fundamental parts of the modern web. But, the often-overlooked component of this ecosystem that has truly enabled the web to scale to billions of users and transactions is load balancers.

Ruby has always been known for the productivity it brings to its developers. Alongside features such as elegant syntax, rich meta-programming support, etc. that make you productive when writing code, it also has another secret weapon called TracePoint that can help you “debug” faster. In this post, I’ll use a simple example to show you 2 interesting facts I found out about debugging.

Tired of waiting for sluggish HTTP requests to complete before your backend code can proceed with other things? Sanic is an asynchronous web framework in Python, that is built to be fast. In a world where Flask and Django are the most preferred web development options in Python, Sanic is the new kid on the block. It’s a promising alternative that is not only faster but also delivers efficiency, simplicity, and scalability.