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.

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.

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.

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.

SentryOne Document supports multiple metadata sources, and we plan to expand available providers in the future. But what if you want to add a metadata source that isn’t currently supported? This is where SentryOne Document’s Custom Metadata Import, available in both the Software and Cloud edition, can help. Leveraging this provider, you can manually insert any metadata source—DB2, REST API, or others.

As a consumer, you know how you respond to slow sites. You hit the back button or close the browser. As a business owner, you’re well aware of this. You’re a consumer, too, after all. So, you know page load time and conversion rate are related. But how exactly? How does it affect the bottom line? In this article, we’ll analyze how page load time affects conversion rates and by how much.

DevOps has great potential; when it’s done right, it offers organizations improved collaboration, quick innovation, better quality, and shorter delivery cycles. But the reality is that some businesses don’t carry the DevOps process through to the data layer.