According to the U.S. Bureau of Labor Statistics, employers are losing more than four million workers every single month. That, coupled with the record number of 11 million open jobs, has left businesses across the board scrambling to crack the code and find a way to not only attract top talent – but, more importantly – keep them from jumping ship at the next best opportunity.
One of the common challenges when doing performance testing is the difficulty of correlating the metrics of your application with your testing results. Having available QA, infrastructure, and application metrics together allows engineering teams to better understand the behavior of their systems during the testing, helping to detect and prevent potential issues in their applications.
Many of the multi-faceted applications development teams deploy every day are loosely coupled and every service exists to power another service. Most teams developing fullstack applications know that testing the communication between these services essential. Part of the process is testing HTTP request endpoints, and this tutorial focuses on exactly that. I will lead you through learning how to extend the k6 framework to test our HTTP endpoints.
I don’t usually do blog posts on news stories, but this one has the potential to impact a lot of people, so I thought it was worth taking a closer look. The top-level story is that Microsoft announced it will not be releasing Hyper-V Server Free as part of Windows 2022. However, if you’re already using Hyper-V Server Free 2019, you can continue to do so until 2029. Hyper-V Server Free is basically a Windows Server Core on which Microsoft has pre-installed the Hyper-V role.
NinjaOne released our custom field functionality in 2021, adding a new level of flexibility, customization, and automation power to our platform. Custom fields are an advanced feature that requires setup to use, but once you start, the power and flexibility of this feature is almost limitless. In this blog piece, we’ll walk you through a powerful use case for custom fields in NinjaOne. Refer to part one of this series for a quick overview of NinjaOne Custom Fields.
When deploying cloud-native applications to a hybrid and multi-cloud environment that is protected by traditional perimeter-based firewalls, such as Palo Alto Networks (PAN) Panorama, you need to work within the confines of your existing IT security architecture. For applications that communicate with external resources outside the Kubernetes cluster, a traditional firewall is typically going to be part of that communication.
