Operations | Monitoring | ITSM | DevOps | Cloud

With over 58K stars on GitHub and over 2,200 contributors across the globe, Kubernetes is the de facto standard for container orchestration. While solving some of the key challenges involved in running distributed microservices, it has also introduced some new ones. Not surprisingly, when asked, engineers list monitoring as one of the main obstacles for adopting Kubernetes. After all, monitoring distributed environments has never been easy and Kubernetes adds additional complexity.

Google “SCOM and Azure” and the top hits will tell you all about “Moving from SCOM to Azure Monitor”, “Changing of the guard…”, and “Microsoft explains why it replaced SCOM with Azure Monitor” etc. If you only read the marketing, you’d be forgiven for thinking SCOM is being replaced. Microsoft’s marketing push on Azure Monitor has no doubt caused some uncertainty about the position of SCOM.

JFrog Artifactory Cloud on AWS is a hosted solution for developers and DevOps engineers that provides complete control, insight and binary management throughout the software development lifecycle. DevOps teams have transparency and control of their entire build and release process, all with the power of cloud-based development. We are excited to announce a set of three AWS Quick Starts to easily deploy Artifactory Enterprise in a highly available (HA) configuration into AWS.

With so much competition in the world of e-commerce, managing to reach the level of exposure targeted and to maintain your site visitors engaged isn’t easy. You need to use effective strategies that allow you to boost the appeal of your platform, maintain rankings up and decrease bounce rates.

Due to a number of vulnerabilities found in the version of Apache we bundle with CFEngine Hub, we have upgraded the CFEngine Hub packages to use an updated version of Apache. We upgrade from Apache 2.4.39 to Apache 2.4.41. We are now releasing a new version, CFEngine Hub 3.12.2-5. Only new Hub packages are being released, as no other packages are affected by these vulnerabilities.

One of the best practices for running Prometheus in production environments is to use a highly available setup, in which multiple Prometheus instances all scrape the same targets. This means multiple instances have all your metrics data, so if one fails, the data is still available on another. Ideally, each instance would run on a separate machine.

We’ve all experienced it – executives with unrealistic expectations who vastly underestimate the amount of time our work can take. Most of us assume that to be the exception and not the norm. But when it comes to monitoring and troubleshooting, that seems to be the all too commonplace.