The API Traffic Viewer for kubernetes
Deep visibility and monitoring of all API traffic and payloads going in, out and across containers and pods inside a Kubernetes cluster.
Reduce complexity, troubleshoot microservices and detect anomalies
Deep visibility into Kubernetes internal API traffic
View all API traffic and payloads going in, out and across containers and pods inside a Kubernetes cluster
Real-time and historic retrospective investigation
Search all real-time and historical recorded API traffic and payloads using a comprehensive query language.
Services and API discovery
Autogenerated API and service inventory, inferred from API traffic and documented in swagger-like format.
Service dependency map
Instant service dependency mapping through real-time API traffic analysis.
Detect anomalies and trace to source
Monitors all API traffic and payloads to find API drift and API anomalies and trace them down to source
Frictionless with minimal performance overhead
Ready to run on large production clusters, works instantly, on-demand with no need to instrument code, install an agent or use a proxy.
Frequently Asked Questions
What was the genesis of Kubeshark?
Kubeshark (fka Mizu) was originally developed by UP9 and then open sourced in late 2021.
Who is behind Kubeshark?
The project is actively developed and maintained by individuals from the same team that originally developed it.
What about new features and use-cases?
We are committed to invest in Kubeshark for the long haul, accelerating the pace of development and supporting relevant use-cases. If you think of any, talk to us.
What's Kubeshark license?
Kubeshark uses the Apache-2.0 license
Can we contribute code to Kubeshark?
We ❤️ pull requests! Check out our CONTRIBUTING.md page for info on contributing changes.
Why the name Kubeshark?
We loved using Wireshark back in the day. Kubeshark is like Wireshark re-born for Kubernetes.