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.