Every year, we take time out of our everyday activities to join thousands of techies just like us for the biggest event of the season–AWS re:Invent. For one week at the end of November, industry leaders gather in Las Vegas to learn about new technologies from AWS as well as other partners in the cloud, DevOps, and IT spaces. The new technology, innovative ideas, and smart, ambitious people we have met over the past few years have been priceless for all of us at Logz.io.

Before the release of Java 9 and 10, there were several limitations to deploying and monitoring Java in Docker. This post explores how the latest versions of Java address the most common of these limitations, and includes examples of how to make the most of monitoring Java in Docker.

Global Service Monitor (GSM) checks the availability of web-based applications from different geographies across the world. Why is that important? It gives an insight in to the end user’s experience, and how well the application works for them. It also allows the monitoring expert to isolate network from application issues. And the best news? SCOM takes that awesome data from GSM and beams it into the console.

AppDynamics has been hard at work innovating for enterprises that rely on SAP technologies. As a leader in CRM, ERP, SCM and other software areas, SAP is a critical system for many organizations. The company continues to gain market share, even in categories with more established players. And with its massive acquisition this month of Qualtrics, a pioneer in experience management software, SAP is preparing to enter yet another market.

Not long ago, we told you about Pivotal Cloud Foundry (PCF) buildpacks and service brokers, and all the ways you can deploy AppDynamics agents in a PCF environment. Buildpack is the key concept here. When you do a deployment to PCF, the buildpack is your foundation. You include the app with the buildpack, which incorporates all the logic needed to connect to various PCF services.

In the United States, it’s almost that time of year again where we count our blessings and give thanks. For retail workers, it’s also that time of year where they prepare for the onslaught of eager shoppers who waited hours in line to run into stores to get their hands on doorbuster deals (sometimes knocking down the employees in the process).

One of the major developments in software design and delivery over the last few years has been a movement away from monolith applications towards microservices. One of the sticking points I’ve seen on numerous microservice applications is logging. There are some unique challenges with microservice logging that need to be addressed. In this article, we’ll look at how we can make logging in a microservice as painless as in a monolith.

With so many choices available to us today, choosing log management software that’s just right for us has never been simpler. That is, if you know exactly what it is you are looking for. But for many users, the sheer amount of computer programs that perform the same tasks, and seem so similar(sometimes almost identical) to each other, can quickly become off-putting and confusing.

Founded by twin sisters in San Francisco well before the city became the focal point of tech, Benefit has been a refreshing and innovative answer to cosmetics customers for over 40 years. The company is a major player in this competitive industry, with a presence at over 2,000 counters in more than 30 countries and online. In recent years, Benefit has undergone a swift digital transformation, with a popular eCommerce site in addition to their brick-and-mortar stores.

When network hardware vendors issue device recalls, field notices, or security alerts, the implication can be massive for MSPs. Take the 2017 clock signal issue, for example. That huge recall of Intel microchips was a large-scale vulnerability for tons of devices—and meant MSPs had to figure out which devices were affected on which client sites.