Operations | Monitoring | ITSM | DevOps | Cloud

You have nested JSON in your logs. When you query body.event.type = "user_action", it fails. Here's why and how to fix it.

In our previous post, we explored the urgent need for intelligent automation in network automation, specifically how the Model Context Protocol (MCP) enables AI agents to dynamically discover and interact with the necessary tools. But access to tools is only part of the equation. To truly operate autonomously in complex environments, agents need not only connectivity but also intelligence.

Back in 2018, I wondered (perhaps loudly if SD-WAN was just IT’s hype-of-the-year, destined for the same eye-rolls as signature-based antivirus and GDPR compliance drives. Even then, I knew we couldn’t let messaging fatigue blind us to real technology shifts. Fast-forward to 2025: SD-WAN (Software-Defined Wide Area Network) not only stuck around, but became the springboard to something far bigger – SASE (Secure Access Service Edge).

Log analysis and management tools have become essential in troubleshooting. With log analyzers you can extract meaningful data from logs to pinpoint the root cause of any app or system error, and find trends and patterns to help guide your business decisions, investigations, and security. If you’re not already using such a tool, now is the time to start looking for one.

Thanks for using the NiCE Log File Management Pack. We know it’s a favorite among experts building custom SCOM Management Packs. But here’s a quick question: When was the last time someone checked your custom Management Packs for security vulnerabilities, performance bottlenecks, or health risks?

If you’re unfamiliar with AWS Summits, these are conferences that occur on a yearly basis in different cities. The events are mostly used to announce new products and technologies. This year, the theme was AI, as evidenced by the keynote, a large majority of the talks, and a walk around the vendor floor. The keynote talk was hosted by Swami Sivasubramanian, VP of Agentic AI at AWS.

A recent BBC article, “Weak password allowed hackers to sink a 158-year-old company,” outlined a serious security lapse. This case reinforces the message that we, at Teneo, advocate every day: true resilience comes from defense in depth, i.e. policy, product and process, not just tools at the edge. In a recent customer engagement, we discussed a transition from VPN to ZTNA. While ZTNA offers enhanced security including continual checking, improved segmentation and a minimized attack surface.

Dynatrace is a powerhouse for application performance monitoring and business analytics. But for many organizations, its power comes with a significant challenge: as applications scale across complex hybrid environments and diverse tech stacks, the sheer volume and variety of logs, metrics, and traces sent to the platform can explode, leading to staggering and unpredictable costs.

Zero Trust is more than a buzzword in today’s cybersecurity playbook, it’s a strategic imperative. Federal agencies, defense operations, and civilian infrastructure providers are all under mounting pressure to deploy Zero Trust Architecture (ZTA) frameworks that are not only compliant but truly effective. But there’s a problem: Zero Trust can only succeed if it’s built on real-time, actionable insight. That means eliminating blind spots.

URLs) receive spiky traffic:. The Healthchecks open-source project includes a fully functional, tested and type-annotated ping handler written in Python. On self-hosted Healthchecks instances, when you send an HTTP request to a ping URL, a Django view collects and validates information from the request, then uses Django ORM to update a Check object in the database and insert a Ping object in the database. This approach is good for tens to low hundreds of requests per second, depending on hardware.