Operations | Monitoring | ITSM | DevOps | Cloud

As we shift enterprise computing to the cloud, the need for database migration increases—but with this comes the inherent challenges of migration and the need to plan. Moving to the cloud can come with more risks and obstacles than migrating a database within a data center or from one on-premises data center to another. If a business isn’t fully prepared to migrate, they’re almost certain to run into issues.

Security is everyone’s responsibility. That’s it. That’s the whole point. (I may be spending too much time with Leon, but it had to be said.) If you have a security team, or even just one person who is tasked with security, it’s easy for the rest of the team or department to fall into a trap, thinking there’s nothing more you need to do. You’re wrong.

If you’re using SQL Sentry regularly, there’s a great event management feature that provides a lot of value for our advanced users. I often find the SQL Sentry Event Calendar isn’t being used as often as it once was. The Event Calendar lets you view historical and future events, drill down into event failures, and reschedule jobs using drag and drop all from within the SQL Sentry desktop client. In addition, you can create custom views of events you need to reference frequently.

H.L. Mencken once famously wrote, “…there is always a well-known solution to every human problem—neat, plausible, and wrong.” More than just a pithy way to frame the entire concept of “cost containment” (whether network-specific cost, the broader category of IT, or the cost of anything else, to be quite honest), it’s an integral aspect of what I’ll be proposing in this and subsequent articles in this series.

Today we’re going to talk about logging with Kubernetes on AWS using CloudWatch and SolarWinds® Papertrail™. We’ll cover setting up Papertrail, installing and configuring the rKubeLog package, viewing the logs in the Papertrail event viewer, and cross-checking those logs with the ones we see with kubectl. From there, we’ll set up a few different alerts.

A few years ago, monitoring was simple. We had all our servers somewhere in the data center; we just had to install a monitoring tool and gather all the data from every server. Things changed when we started moving to the cloud and then to containers. Today, we often need to monitor a variety of different sources. A “server” can be a physical machine, virtual machine, container, or even a serverless application. Therefore, our approach for monitoring needs to change.

Heading to the gym, you have access to so many amenities in one place: cardio equipment, private studios, a pool, free-weight area, a basketball court. Imagine if those conveniences were located at separate facilities, forcing you to have separate memberships and make different trips to achieve a well-rounded workout – it doesn't bode for the best experience. In a different context, think about your employees' experience as they search for answers across multiple platforms for service providers.

Buying a home requires thoughtful planning and takes a significant amount of time and resources. Beyond your list of must-haves, you’ve likely kept tabs on houses of interest to you, the state of the market, how safe the neighborhood is, and more. Another factor in your decision is how the house is equipped to grow with you—will it continue to meet your needs in the next five years? It’s critical to establish a sound foundation that works for you today and in the future.

"No one likes documentation", chirped the little blue birds. The bird quotes in the image above are all taken from real tweets and are listed below for accessibility: I can't argue with "liking to write documentation" being a rare skill, since so many people are vocal about disliking it. That tweet might prove to be true, in which case, technical writers should simply be more appreciated for the rare gems that they are. In this blog post, however, I’m going to explain.