Operations | Monitoring | ITSM | DevOps | Cloud

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.

Last week, we hosted a webinar on the easiest way to right-size – and safest way to overhaul – your architecture. One of the scenarios we’re seeing come up more and more with prospects and customers is the need to update your architecture, and particularly your security architecture, as new needs and threats arise. As I’m sure you all know, that can be a real hassle, put a strain on your resources, and put your security posture at risk if it isn’t done well.

AWS OpenSearch is a project based on Elastic’s Elasticsearch and Kibana projects. Amazon created OpenSearch from the last open-source version of ElasticSearch (7.10) and is part of the AWS system. The key differences between the two are topics for another discussion, but the most significant point to note before running either distribution is the difference in licenses. ElasticSearch now runs under a dual-license model, and OpenSearch remains open-source.

When it comes to your analytics tools, would you say they’re getting easier to manage overall, or is it increasingly difficult? Can you easily scale to meet new compliance requirements, or is there so much custom work required that the pace of change is too much for your team to handle? Do you feel in control over how and where your observability data flows, or do you feel beholden to your vendors? This blog post will shed light on how you can ease the strain on your downstream systems.

Last year, International Data Corporation released its Data GlobalSphere Forecast, 2021-25, in which it outlined the projected 23% compound annual growth in data, leaping to 175 zettabytes of data globally. So the natural question becomes, what will the world do with that much data? And, more importantly, what can your business do with your data?

It’s 3pm on a Wednesday, and you’re really just done with the week already. You hear that “ping” from your Slack and know that you set notifications for direct messages only, which means, ugh, you have to pay attention to this one. It’s your boss, and she’s telling you to check your email. Then you see it, the dreaded audit documentation request. This will take you the rest of today and most of tomorrow.

The recent release of Grafana 8.5 marks the start of enabling the jump from traces directly to Splunk logs. It’s a big leap that now allows you to draw a straight line between your traces — whether they are coming from Tempo, Zipkin, or Jaeger — to even more third-party logging data, all from the comfort of your traces view. Previously, the Grafana trace to logs enablement included only Loki logs.