Today we announce the newest additions to CFEngine. CFEngine 3.16 brings several improvements, bug fixes, and new features. The theme for this release has been compliance, and it notably includes a new category of reports for proving compliance to regulation and other compliance frameworks in high level, easy to read reports. If you are interested to learn more about CFEngine, schedule training, or hear about pricing options, feel free to reach out to us!
There is a value perception gap in IT. It can be a struggle to get past the historical notion that IT is a cost center, rather than a strategic arm of the business. E&Y recently surveyed 300 senior IT professionals around the globe to understand how they are perceived by their C-level executives. The survey found that 67% of CIOs engage with executive peers on matters of budgetary issues and infrastructure management. Far fewer, only 36%, engage in matters of business performance and challenges.
Traditionally, IT service management was limited to legacy platforms and infrastructure. Due to a lack of process, interacting with IT teams was frustrating and difficult, resulting in the workforce becoming less engaged, and the gap between the IT team and business growing even further. Since IT service management was already a complicated task for most IT teams, COVID-19 only exacerbated the repercussions.
Deploying and monitoring performance for an entire Kubernetes cluster can be complex. To simplify the process, we’ve added service discovery functionality to eliminate complex configuration, in addition to more advanced monitoring for viewing activity inside containers. Service discovery identifies k8s pods running on a cluster and immediately starts monitoring system performance. All containers are identified, regardless of complexity.
We all know that Prometheus is a popular system for collecting and querying metrics, especially in the cloud native world of Kubernetes and ephemeral instances. But people forget that Java has been running enterprise software since 1995, while Prometheus is a relative newcomer to the scene. It was only created in 2012! Even though Java has had its own metric collectors since before Prometheus was born, none of our new environments speak its (metric) language. How can you bridge that gap?
Zac Propersi, Engineering Manager at Sentry, can tell when a page is not loading as fast as it should — just by looking at it. While working on our new Metric Alerts feature, Zac noticed that the alerts pages were rendering slowly. Being the super Sentry user that he is, he wrote a custom query in Discover to see just how slow the transactions were.
It’s no secret that AWS Lambda adoption has grown steadily since AWS first released it in 2015—and for good reason. The benefits of adopting Lambda are many: leveraging Lambda eliminates the need to provision and manage servers, enabling teams to just focus on their code without the mental and operational overhead of worrying about the underlying infrastructure.
Errors are undesirable for users and you should do everything in your control to keep users away from them. However, they are of utmost importance for developers. They allow developers to understand the inaccuracies and vulnerabilities in their code by alerting them when their code breaks. They also provide relevant information about what went wrong, where, and what can be done to make amends.
Large-scale cloud applications are usually built using interconnected services that can be rather hard to troubleshoot. When a service is scaled, simple logging doesn’t cut it anymore and a more in-depth view into system’s flow is required. That’s where distributed tracing comes into play; it allows developers and SREs to get a detailed view of a request as it travels through the system of services.
