Operations | Monitoring | ITSM | DevOps | Cloud

From Atlassian JSON to Actionable Audit Insights

Atlassian audit logs carry high-value security and operational signals, yet the raw format makes them hard to use in day-to-day investigations. Nested JSON, arrays inside arrays, and localization keys turn routine questions into slow, manual work. For lean Security and IT teams, that friction shows up as delayed triage, fragile dashboards, and alerts that fire without enough context to act.

Taming Atlassian Audit Logs: Processing messy JSON to enable operational insights

Atlassian’s audit records are data-rich, but messy. In this data-driven deep dive, Eddy Gurney from NetScout shares what it took to get them into Graylog. He walks through four pipeline approaches and why each fell short, then shows how moving parsing to the edge with Filebeat unlocked Graylog. With clean, flattened events flowing in, alerts and dashboards turn “noise” into operational visibility. You’ll also see how Sidecars makes config rollout easy, plus what changes to make if you’re on Atlassian Cloud instead of Data Center.

Kubernetes Logging Best Practices

You’re sitting at your desk, typing away, when all of a sudden you hear a “ping!” Unfortunately, you have a browser with fifteen tabs open, a task management application, email, messaging applications, and calendars all open, making it difficult to know exactly which technology just pinged you. To identify the source, you open your system settings and look at the notifications section to see which ones you allow to make a sound.

Introducing The First Graylog Helm Chart Beta V1.0.0

Running Graylog on Kubernetes has been possible for a while, but let’s be honest: it usually involved a fair amount of DIY. Custom manifests, duct-taped values files, and more than one late-night kubectl describe pod. That changes today. We’re releasing the first-ever Graylog Helm chart for Kubernetes — now available in beta.