Cribl announced enhancements to the entire Cribl product suite to simplify and personalize all observability data, making it easier for different stakeholders within the enterprise to get data and insights tailored to their unique needs on-demand.
These new features open up the power of observability data to a broader set of users via self-service tools while enabling administrators to deliver maximum value to all teams throughout the organization with minimal effort.
"With enterprise telemetry data, value is in the eye of the beholder. Different stakeholders, each with their own unique data visualization needs, have struggled to quickly find and shape the data they need to achieve success," said Cribl Co-Founder and CEO Clint Sharp. "With this newest release we make it simple for our admins to centralize and control data ingestion, and then enable tooling stakeholders to select which approved data streams are interesting to them and empower them to shape and transform the data to suit their environments."
Cribl announced Stream Projects, a self-service model that allows a variety of users to securely access any observability data without requiring new agents or changes at the data sources. With Cribl Stream at the core of an enterprise's observability architecture, administrators already have complete control over their observability data. Stream Projects adds to this control by enabling administrators to simply set up projects based on department need and shape the data in that project to be optimized for a particular use, allowing new users to subscribe only to the data that is important to them. Available in Summer 2023, this self-service model reduces dependency on the administrator to onboard more users and tools, and reduces the time-to-value for the user.
Cribl is also re-launching Cribl Curious in March, a self-service tool where users can find answers to questions asked and answered by the community. Cribl Curious takes the most frequent user questions and makes them easily searchable for current and new users. The new Cribl Curious also supports user group capabilities to get users together in real life at local meetups. Cribl's Slack community will continue to be a resource for more complex questions and a place for users to engage with each other and the Cribl team.
Additional Product Enhancements
- Cribl Stream 4.1 – In addition to Stream Projects, Cribl Stream now features support for Open Telemetry solutions, the ability to log in to Cribl using an Identity Provider of choice (Okta, Azure AD, etc.), enhancements to WEF Collector, and new Cribl Search destination.
- Cribl Edge 4.1 – New features include expanded container support, new journal support, Windows enhancements, and deep visibility into how Edge nodes are operating at fleet/sub-fleet level.
- Cribl Search – Cribl Search now features query target expansion, support for searching and exploring data and then forwarding it via Cribl Stream to any destination, and an improved user experience featuring expanded operators/functions, client-side preview, and results shaping and performance enhancements.
- Cribl.Cloud – Users now have the ability to assign many users to owner-role privileges, create additional Cloud Worker Groups, and securely drive Cribl Stream and Cribl Edge through code using APIs.
The Latest
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...