Operations | Monitoring | ITSM | DevOps | Cloud

It is always essential to make sure all your assets and inventory records are accurate and up-to-date. But, the rapid increase of technology such as mobile devices and assets-on-the-go used both within and outside of the office made the asset management process complex. However, with the help of spreadsheets and on-premise solutions, you can manually keep track of your assets. But, these methods are time-consuming and disorganized and don’t provide complete visibility and insights.

You’ve probably seen Rush Hour, a logic puzzle where you have to slide cars and trucks out of the way to steer the red car towards the exit. In real life, when your customers are responsible for tracking hundreds or thousands of data points from dozens of valuable, mission-critical sensors, you’re tracking engine speed, network signal level, distance from the RF, and more—and not just through traffic but across continents.

Break out your buzzword bingo cards, it’s time to talk about SASE or Secure Access Service Edge. Pronounced “sassy,” SASE has become one of the hottest topics in networking and security over the last three years. The basic idea is great: all your security and network services are on one platform. The problem comes when you get into the specifics. When does a set of services go from “not SASE” to “SASE”?

Azure Advisor analyzes your configurations and usage telemetry and offers personalized, actionable recommendations to help you optimize your Azure resources for reliability, security, operational excellence, performance, and cost. Azure Advisor is a free service and can be accessed via the GUI on the Azure portal where recommendations are collated and can be manually examined. Azure Advisor makes recommendations for potential improvements in several areas, including.

Service ownership, a DevOps best practice, is a method that many companies are pivoting towards. The benefits of service ownership are varied and include boons such as bringing development teams much closer to their customers, the business, and the value being delivered. The “build it, own it model” has tangible effects on customer experience, as developers are incentivized to innovate and drive customer-facing features that delight.

Welcome to another month of What’s New in Sysdig in 2022! I’m Joshua Ma, a Customer Solutions Engineer based out of sunny Los Angeles. I joined the Customer Success team at Sysdig five months ago. After having my first taste of K8s, containers, and Falco at the North America KubeCon/CloudNativeCon in 2019, I haven’t looked back since!

In the quest for business transformation and digital modernization, organizations have rapidly adopted devops frameworks, microservice architectures, serverless technologies, and containerized infrastructures. However, they have realized that legacy tools cannot adequately address the newer security and monitoring challenges associated with modernization. Sysdig’s mission is to make every cloud platform secure and reliable from source to run.

Innovation in DevSecOps must keep pace with the speed of the dynamic, volatile modern cybersecurity environment. Yesterday’s solution worked beautifully…yesterday. What has it done for me today? Continual iteration and speed are paramount, but they’re not without risks. As a SaaS provider, how do you know that the latest evolution of your product works at scale? How do you know that it works at all?

Efficiently retrieving Kubernetes metrics is the beginning of cluster performance optimization. Cluster metrics such as logs and resources descriptions are crucial as they map the health of your cluster. There’s a Kubernetes tool called K9s that lets you access your Kubernetes cluster metrics swiftly using short keys. K9s prioritizes aesthetics and performance as it displays its contents and functions in an aesthetically pleasing UI.

In every workplace, most work gets done at the most cluttered desks. Yet the business also requires an orderly front office to run efficiently. It’s much the same with your DevOps pipeline environments, as the rough and tumble process of innovating code must ultimately produce cleanly released applications. Continuous integration means that developers perform many builds each day, but few of those builds will advance to production repositories.