Operations | Monitoring | ITSM | DevOps | Cloud

On July 4th we celebrate. We celebrate freedom of movement, freedom of assembly, removal of excessive taxation, and much, much more. But what about digital independence? Removing the tyrannical yoke of control over your observability data. Authoritarian vendors restrict access and movement; they dictate proprietary formatting and even limit what can be commingled with your data, then apply enormous tax burdens (i.e. license fees) just to store your data.

But many businesses don’t have insight into where that money goes and whether or not they’re pricing their products accordingly. CloudZero Founder and CTO Erik Peterson sat down with Erik Carlin, Founder and CPO at ProsperOps, to talk about the transition in cloud cost optimization from 1.0 to 2.0. They explored what data engineering teams need to make informed buying decisions, how to turn data into actionable intelligence, and why you should view cloud costs as an opportunity for ROI.

Every business today is now a tech company, regardless of the product or service they offer. While Tesla is a tech company that manufactures automobiles, one may argue that Footlocker is also a tech company that happens to sell sneakers.

“Time is money” couldn’t be truer than in managing cloud costs. By way of proactive anomaly detection, a chance is given to save time that could have been spent on issue recognition and resolution. Anomaly detection for the Cloud can be tricky since there can be changes in prices & data on billing history anytime. Not to mention, seasonality can mess things up as well.

Software testing is a rapidly evolving landscape where automation has replaced traditional manual practices significantly in recent years. Artificial intelligence (AI) and machine learning (ML) advancements introduced a groundbreaking approach to software testing known as autonomous testing. This article aims to provide a comprehensive guide on autonomous testing tools, highlighting their benefits, and the top tools available.

We’ve long believed that incidents (and technical team cultures) improve when more people are empowered to declare, follow, and contribute to their resolution. But not everyone in an organization needs to be able to manage the processes, rules, and settings a company enforces for their incident programs.

This month, Sysdig has released Process Tree which enriches the Events feed for workload-based events. This helps with identifying all the processes that led up to the offending process. This is in technical preview status. Sysdig has also released Sysdig Secure Live.

In recent years, network operations teams have had to contend with several critical challenges, including: In response to these challenges, teams are increasingly turning to SD-WAN. The market for SD-WAN is massive, and continuing to grow, potentially reaching $47 billion by 2031. Through SD-WAN technologies, organizations are able to realize a number of benefits. However, these benefits aren’t a sure thing. In fact, many teams encounter challenges with their SD-WAN implementations.

We recently introduced a new version of InfluxDB, rewritten from the ground up to improve performance across the board. As with any undertaking of this nature, developers will need to make some adjustments to their applications in order to incorporate the new database. We even faced this challenge internally. We had many Telegraf instances sending data to legacy versions of InfluxDB.

How can anyone forget the photos and images of mounds of luggage sitting wherever they could find a spot at most major airports, back during the winter storm of 2022? And what about the thousands of stranded passengers in dismay during the holidays, with plans and gifts that literally couldn’t get off the ground?