Loggly announced Loggly 3.0, a unified log analysis and monitoring solution designed for companies building modern software applications running on private or public clouds and serverless architectures.
Combining new metrics and monitoring capabilities with deep log analysis and one-click access to source code, Loggly 3.0 gives DevOps teams one-stop visibility to identify and solve problems, collaborate on fixes, and report to stakeholders.
“Our customers are facing exploding volumes of machine data generated by dynamic infrastructure, microservices, and devices, as well as the constant change of continuous delivery,” said Manoj Chaudhary, CTO at Loggly. “Their monitoring toolkits have grown to address the data overload, sometimes creating even more complexity. This is what is driving convergence in the DevOps ecosystem between logs and monitoring. Loggly 3.0 offers a simple and comprehensive path to dealing with data and tool overload, and it builds up DevOps teams’ efficiency and collaboration.”
Loggly customers can now address three distinct needs with a single cloud-based service:
- Proactive monitoring for potential issues, anomalies, or suspicious activity across their code and infrastructure. New charts and dashboards reveal the full story and can be created in just a few clicks. In addition to the ability to display any log-resident or Amazon CloudWatch metric, Loggly will support metrics collection using the collectd daemon in the fourth quarter of 2017.
- Deep-dive investigations, discovering root causes by searching and filtering on individual log events. A new integration with GitHub connects insights from dashboards to logs to individual lines of source code, without any additional instrumentation. The GitHub integration initially supports Java, JavaScript, and Python.
- Data analysis and visualization to characterize software performance, answer key business questions, spot trends, report on KPIs, and track SLA compliance. Users can work in Loggly without support from a dedicated administrator.
The new GitHub integration builds on previous Loggly integrations designed to improve teamwork by incorporating data and analysis within the tools that software teams use every day, including New Relic, PagerDuty, Slack, Atlassian HipChat, and Atlassian Jira Software.
Benefits of Loggly 3.0 include:
- Reduced complexity with one unified solution for monitoring, visualization, and log analysis.
- Improved service quality through proactive monitoring of metrics across the entire software stack, along with the deep analysis needed to know where to make improvements.
- Shorter mean time to resolution (MTTR) through rapid root cause analysis and tighter connections between metrics and relevant events.
- Better teamwork through common insights on shared dashboards, comprehensive reporting, and integration with the DevOps toolchain.
The Latest
In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...