How is your organization handling Kubernetes observability? What tools are you using to monitor Kubernetes? Is it a time-consuming, manual process to collect, store and visualize your logging, metrics and tracing data? And, what are you actually getting out of all that investment?
At Logz.io we’re trying to make this process easier for customers who are serious about Kubernetes observability. We’ve made significant investments in this area for Kubernetes use cases. That’s why we recently hosted a webinar on the topic: Full Kubernetes Observability in Minutes.
For Logz.io customers, the way Kubernetes observability was handled was different before November 2022 than it is now. While Logz.io handled telemetry data processing and storage out of the box for customers, the initial collection process and latter visualization and analysis needed to be handled manually by customers.
All that changed with our new platform launch. Now, Logz.io handles all three of the aforementioned steps of the Kubernetes observability process—collecting, data processing and storage, and visualization and analysis.
“You can begin monitoring and troubleshooting Kubernetes with very minimal configuration and overhead,” Charlie said. “Logz.io essentially handles these steps for you. You can set up the whole thing in minutes.”
A key component of this process is the Logz.io Telemetry Collector. With this new feature, customers can simplify collecting log, metric and trace data. Processes and setup that used to take hours or days for even seasoned professionals can now take minutes.
Telemetry Collector is based on open source technologies, bundling OpenTelemetry and Fluentd into a very simple deployment. Telemetry Collector currently supports AWS and Kubernetes telemetry data, with more to come.
“We’re going to add integrations with GCP and Azure, with new capabilities such as auto-instrumentation coming in the future,” Doron said.
Once you send your data to Logz.io, the next step is around data visualizations. Before the launch of Kubernetes 360 late in 2022, customers would be required to manually create log and metric monitoring dashboards to monitor clusters.
While customers are still welcome to do that, we’re now offering Kubernetes 360, an out-of-the-box dashboard to unify metric and log analysis for Kubernetes.
“Kubernetes 360 automatically monitors all the key metrics that any Kubernetes user would want to see,” Charlie said. “These include pod failures, CPU, memory, log error rate and others.”
In the future, the plan is to add a security layer to Kubernetes 360 so customers can see beyond observability data, as well as the ability to see financial data.
“We believe in open source,” Doron said. “We see our customers’ environments and they have their own Elasticsearch, OpenSearch, Grafana for metrics and Jaeger for traces—we still have these capabilities in our platform. But here, we have a way to consolidate everything together to see what’s happening in your Kubernetes cluster.”
We then went through a full demonstration of Telemetry Collector and Kubernetes 360, including walking through documentation and the product itself. We also took audience questions. Find a consolidated version of the demonstration here.
Watch the full webinar to gain an understanding of how you can get better observability with Logz.io, a feature overview of how to collect Kubernetes data with Telemetry Collector, full details on how to visualize Kubernetes telemetry data with Kubernetes 360 and more.
Telemetry Collector and Kubernetes 360 combine to make a truly seamless Kubernetes monitoring experience. Deploy the agent in minutes, and your data will auto-populate Kubernetes 360 so you can begin getting insights from your clusters.