Operations | Monitoring | ITSM | DevOps | Cloud

Given the strategic importance of the cloud and size of cloud expenditures, it’s critical for enterprises to have solid controls in place to manage it all. According to our latest research, however, while most organizations agree with that sentiment, very few have put it into practice. There are distinct but related disciplines that come into play: FinOps and cloud governance. In this two-part series, we explore current state of each.

Every month, our team works on two major fronts: shipping new features asked by users and iterating on shipped features to make them better for existing users. Last month, our team worked closely with users to ship a lot of product improvements both in UI and backend performance. Alongside that, we have been working on metrics builder and log management, two major feature upgrades to SigNoz.

Software Asset Management (SAM) is a topic that is seldom discussed in conversations about the importance of IT Asset Management. And yet it's a crucial part of every company's organizational efforts. This is because software is more than just installations.

When transferring data between systems, it's extremely important to preserve integrity and confidentiality. There are protocols and procedures to do so. One of them is the Secure Copy Protocol (SCP); which is a method designed to securely pass on digital information. The SCP protocol helps transferring files from a local to a remote host or between two remote hosts.

Two of the most important ITSM practices in today’s IT managerial landscape are asset management and configuration management. Since software and hardware components are at the heart of the service a company provides, understanding how these components work is vital in IT service management. It might sound tricky since management has so many branches that extend anywhere from a company’s resources to its partners, its data, processes, and suppliers.

As systems become more complex and distributed, the total amount of machine data put off by those systems continues to skyrocket. While teams may need access to an ever-increasing scope of machine data to gain insights into their increasingly complicated systems, that same need to access an increasingly large amount of data also creates cost concerns. Those concerns can grow into cost emergencies quickly.

The IT Operations space has a ton of recent advancements, and arguably the most elusive Observability unicorn for many organizations has got to be "AIOps," perhaps with "proactive monitoring" coming in as a close second place. You may be thinking.

The fact that data centers have evolved a lot is undeniable. This has enabled storage evolution and the execution of online applications. Now we often talk about hybrid clouds. *Yes, we don’t even take the time to explain what digital clouds are anymore and we even assume that everyone has their own, small but they have them.But when it comes to doing things big, it’s unavoidable to mention the giant Google Cloud®!

Recently we introduced new feature where you can trigger agent runs and report collection from the Mission Portal UI. This required our daemon cf-execd to behave a bit differently when periodic agent runs occur. Previously the daemon would create a new thread in which to run cf-agent, capture output, wait for completion and move on. We changed the behavior so that the daemon forks itself and then fork/execs cf-agent as before, with the forked cf-execd processing agent run output.

A while back we released version 2 of cfbs, and even though we release versions of this tool quite frequently, without announcing it on the blog, we thought this was a good opportunity to talk a bit about the tool, what’s new and our direction with it in the future. The reason why we called this the “2.0” release is that we are trying to follow semantic versioning, and there were some big new features in the release which could be considered breaking changes.