Operations | Monitoring | ITSM | DevOps | Cloud

Providing breakthrough IT operations requires ITSM, DevOps, and other ITOps leaders to efficiently and economically deliver exceptional employee experiences and high-performing business applications. Achieving these expectations isn’t easy.

In a previous post, we explored the basic concepts behind using Grok patterns with Logstash to parse files. We saw how versatile this combo is and how it can be adapted to process almost anything we want to throw at it. But the first few times you use something, it can be hard to figure out how to configure for your specific use case.

IT Asset Management (ITAM) and IT Service Management (ITSM) are critical for any organization that requires IT capabilities to support business objectives. Both technologies provide IT operational support to an organization; however, the purpose and objectives of these technologies are quite different. Let’s explore the differences and similarities between ITAM and ITSM.

I’ve recently started working on a new project to build a Discord bot in Go, mostly as a way to learn more Go but also so I can use it to manage various things in Azure and potentially elsewhere. I figured it’d be useful to document some of this project to give some insights as to what I’ve done and why. First up was setting up the CI/CD pipeline for it so that I don’t need to worry about it later and can save myself a bunch of time when testing.

We recently announced a license change: Blog, FAQ. We posted some additional guidance on the license change this morning. I wanted to share why we had to make this change. This was an incredibly hard decision, especially with my background and history around Open Source. I take our responsibility very seriously. And to be clear, this change most likely has zero effect on you, our users. It has no effect on our customers that engage with us either in cloud or on premises.

This blog is the second in a two-part series and was adapted from The Enterprisers Project. At a time when CIOs can use cloud infrastructure to turn on new money-making services for customers overnight, how should we measure IT success? Hint: It's not about uptime. In part 1 of this series, we talked about how traditional IT metrics such as server capacity, I/O, utilization, and network throughput are less relevant today in our highly-digital world.

A significant portion of companies have vulnerabilities in their network management practices. These vulnerabilities include a lack of network visibility, configuration backups, proactive network planning, and up-to-date documentation. Despite these vulnerabilities, the majority of IT pros report high confidence in their networks, indicating a potential mismatch between perception and reality.

Work, education, and even many of our leisure activities have all moved on-line at an incredible pace due to current social distancing mandates. The digital backbone of the Internet and the SaaS services that drive our personal and professional lives are now foundational. Ensuring that these systems are operating optimally and securely is of paramount importance.

Innovation in hypervisor technology in the early 2000’s from both commercial and open source projects was the genesis for the public cloud as we know it today. Virtualization and Moore’s law, together with advances in storage technology, mobile and wireless, created a data explosion that continues to accelerate through today.

There’s no question that Elastic has built a truly amazing company, based on the Apache 2.0 open source business model, and on the shoulders of other projects like Lucene. Last week, Elastic announced that, starting with version 7.11, Elasticsearch will now be licensed via SSPL, a license that Mongo released in 2018. So you may be wondering what this all means. Here are what we anticipate will be a few Frequently Asked Questions around this Elasticsearch licensing change.