Logz.io announced the launch of App 360, a new, observability-based approach to Application Performance Management (APM).
App 360, the newest addition to the Logz.io Open 360™ observability platform, delivers all the functionality needed for core APM use cases in an observability solution that is simpler to use and less expensive than traditional APM solutions yet provides full visibility into application health and performance.
APM is broadly defined as tools and systems to monitor and manage the performance and availability in software applications.
“App 360 takes everything that’s wrong with traditional APM and flips it on its head,” said Asaf Yigal, co-founder and CTO of Logz.io. “Whereas traditional APM is heavy, hard to implement, expensive, shackled by vendor lock-in and slow to bring business value, App 360 is exactly the opposite. App 360 is tailor-made for the microservices and Kubernetes era and offers a high-performance observability approach that is easy to set up, easy to use, and less costly than traditional APM solutions.”
App 360 is a centralized interface for visualizing and investigating application performance. Built for distributed microservices architectures running on Kubernetes and other modern environments, App 360 combines logs, metrics and traces from applications, infrastructure and Kubernetes into a single picture. App 360 enables stakeholders to see the right signals and correlate all the relevant information to truly understand their environment, from individual applications all the way down to the CPU level. With App 360, customers can avoid siloed telemetry and quickly achieve full application observability so they can answer difficult questions about the current state of their environments — at a fraction of the cost of other platforms.
“Engineers can now get APM capabilities without APM headaches through a modern, observability-centric technology that doesn’t take forever to implement and gives engineers just what they need to surface and resolve issues rapidly,” Yigal continued.
One of App 360’s major benefits is that it is exceptionally easy to use. Logz.io’s OpenTelemetry-based agent enables automatic service discovery, one-click application instrumentation, and data collection for logs, metrics and traces. From there, the most critical application telemetry data and insights are automatically highlighted within App 360 — making the current state of service performance obvious.
App 360 helps engineers surface issues sooner and debug their services faster. Logz.io’s Service Map and Service List provide a bird’s eye view of performance across microservices architectures. Telemetry data is automatically tagged and organized by microservices so when a problem occurs, it is immediately obvious which services are affected. From there, App 360 provides straightforward paths to investigate problems by correlating the relevant logs, metrics and traces needed to isolate the root cause of the issue.
Another key differentiator from traditional approaches is that every element of the Open 360 platform is optimized for maximum data and cost efficiency. From the platform’s unique Data Optimization Hub to multi-tiered storage, including Cold Tier on Amazon S3, organizations choosing Open 360 with new App 360 capabilities will appreciate significant savings over legacy APMs.
App 360 combines numerous Open 360 capabilities to deliver an innovative approach to APM, including:
- Service Overview: Unifies the essential telemetry data from your infrastructure and applications in a single data analysis interface — all while requiring minimal configuration. Service Overview makes it easy to spot high-level performance trends across your microservices and get fast insights into the current state of your microservices performance in a single place.
- Distributed Tracing: While Service Overview helps you isolate application performance issues across your entire infrastructure and all applications, Distributed Tracing helps you drill down into individual application transaction flows to diagnose the root cause of issues such as bottlenecks and failures.
- Service Map: This updated visualization of topology highlights the data flow, dependencies and critical performance metrics across your microservices architecture. Service Map makes it easy to gather critical troubleshooting context as you investigate production issues.
- Service List: The Service list dashboard centralizes all of your running services, allowing you quickly to detect if and when issues occur. You can use the dashboard to investigate the different services, operations and logs inside each one.
- Easy Connect: Go from zero to full observability in minutes. With Easy Connect, service discovery, application instrumentation and data collection is entirely automated. After deploying the Telemetry Collector — Logz.io’s OpenTelemetry-based agent — on a Kubernetes cluster, Easy Connect will discover every service in your cluster and provide the option to instrument each one.
- Deployments: This new capability can view and track the deployments of a user’s service within Open 360 dashboards. Users gain visibility into when services were deployed, which versions are running and any associated deployment notes to better troubleshoot production incidents.
- Data Optimization Hub: This telemetry data pipeline capability provides a single place to identify, remove or manipulate unneeded observability data to easily reduce costs. Many Logz.io customers remove as much as 50% of their data, saving significantly on observability costs while also limiting data complexity.
App 360 is immediately available to all Logz.io customers, simply ship your tracing data to the Open 360 platform and immediately begin using this critical capability at no added cost.
The Latest
Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...
One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...
As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...
Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...
The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...
Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...
Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to third party services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...
If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...
Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...
APMdigest's Predictions Series concludes with 2026 AI Predictions — industry experts offer predictions on how AI and related technologies will evolve and impact business in 2026. Part 5, the final installment, covers AI's impacts on IT teams ...