Operations | Monitoring | ITSM | DevOps | Cloud

We are proud to announce that Splunk has been named a Leader in the 2025 Gartner Magic Quadrant for Observability Platforms for the third year in a row. In our opinion, our recognition in the Observability category comes on the heels of Splunk being recognized for a tenth consecutive time as a Leader in the 2024 Gartner Magic Quadrant for Security Information and Event Management (SIEM). Splunk was the only vendor named a Leader in both SIEM and Observability for the Gartner Magic Quadrant three times.

Key takeaways In the fast-moving world of CI/CD pipelines, microservice architectures, and container orchestration, software changes rapidly. What exists in a codebase today might be gone next week. At this scale and speed, it’s impossible for development teams to manually track every line of code and every new piece of functionality.

Today’s public sector organizations are tasked with delivering a staggering amount of technology capabilities to support a growing set of digital services, meet IT modernization goals, and continue to protect against a wide range of attack vectors. Cloud technology adoption has played a significant role in ensuring that ongoing IT modernization not only aligns with each organization’s mission-strategic capabilities but also enables efficiencies of scale.

In this blog we are going to address how to use Splunk to monitor security of MCP Servers, a new technology that has been developed by Anthropic and has definitely bridged the use of local applications with Large Language Models (LLMs).

In Part 1, we explored how aligning network visibility with IT service context empowers faster, smarter incident response. But what does this actually look like? Here in Part 2, we’ll go deeper into the challenges of traditional monitoring approaches, and how teams should look to move from fragmented alerts to unified insights – because when ITOps and NetOps can both see the “what” & “why” of the problem, actions become instinct.