Operations | Monitoring | ITSM | DevOps | Cloud

At this point we are well past the third installment of the trilogy, and at the end of the second installment of trilogies. You might be wondering if the second set of trilogies was strictly necessary (we’re looking at you, Star Wars) or a great idea (well done, Lord of the Rings, nice compliment to the books). Needless to say, detecting anomalies in data remains as important to our customers as it was back at the start of 2018 when the first installment of this series was released.

It’s always something, isn’t it? It seems that just as you’ve gotten your organization up to speed with ITAM guidelines, some newfangled idea comes along to stir things up. But IT is (or should be) all about continuous improvement. Stationary things wither on the vine; things that move, evolve. ITAM 2.0 is precisely about keeping things moving along in the right direction. And, like it or not, managing your asset inventory is always going to be open to improvement.

Embracing the cloud is not just a case of improving infrastructure, experts believe, but also a way to drive transformation. Many of the world’s largest financial exchanges are transforming the way they run global capital markets through the adoption of cloud computing technologies. In November, financial derivatives exchange CME Group entered a 10-year partnership with Google that will move CME’s IT infrastructure and markets to the cloud.

Before the pandemic, assets were managed through a spreadsheet or a register and were managed manually by the Asset Manager/IT Agent (in some cases). When the pandemic forced people to work out of their homes, assets management became complex. Manual allocation of assets, monitoring software licenses and upgrades, and keeping track of assets were tedious. It became impossible to manage remote assets without using an asset management solution.

Regardless of economic conditions, IT usually operates under an axiom no one in business ever likes to hear: “We have to do more with less.” Doing more with less is essentially the default position for IT, but when it comes to security operations, that position can have real consequences.

For this edition of my ongoing Grafana Loki how-to series, I wanted to offer up some helpful — and perhaps surprising — facts about using LogQL, Loki’s query language. In case you’re new to Grafana Loki, it’s a log aggregation system created in 2018, and the Loki team has worked with the community ever since to introduce new features and make it easier to deploy.

Given a choice, would you rather wait for a cab ride that’s 25 mins away or look for other options to reach your destination faster? Without a doubt, you would pick the latter, right? Today’s ‘want-it-now’ consumer mentality is driving most technology organizations to rethink how they interact with employees and customers. Employees have consumer-grade expectations for corporate applications, and IT requests at the workplace.

When the capabilities of IT service management are applied to other business functions like HR, Finance, Facilities, Legal, Sales, or Marketing to improve service delivery, it is known as ESM (Enterprise Service Management)

The simple query service (SQS) was one of the first services AWS offered. It’s a managed queuing service that lets you take pressure from your downstream services. You put your items on the queue, and other services can pull them whenever they have the capacity to work on them. It’s a managed service, so you don’t have to install or maintain the software yourself; you just configure a queue and start pushing to and pulling from it. So SQS is very simple to get started with.