[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9935":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":19,"rankGlobal":10,"rankLanguage":10,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":23,"hasPages":23,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":44,"readmeContent":45,"aiSummary":46,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":47,"discoverSource":48},9935,"pixie","pixie-io\u002Fpixie","pixie-io","Instant Kubernetes-Native Application Observability","https:\u002F\u002Fpx.dev",null,"C++",6462,504,75,300,0,2,25,39.11,"Apache License 2.0",false,"main",true,[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,5,41,42,43],"aks","apache-arrow","cloud-native","cncf","distributed-systems","ebpf","eks","gke","golang","kubernetes","machine-learning","metrics","minikube","monitoring","observability","pandas","px","px-run","vega","2026-06-12 02:02:14","[![Pixie!](.\u002F.readme_assets\u002Fpixie-horizontal-color.png)](https:\u002F\u002Fpx.dev)\n\n\u003Cbr>\n\n[![Docs](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fdocs-latest-blue)](https:\u002F\u002Fdocs.px.dev)\n[![Slack](https:\u002F\u002Fslackin.px.dev\u002Fbadge.svg)](https:\u002F\u002Fslackin.px.dev)\n[![Twitter](https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Furl\u002Fhttps\u002Ftwitter.com\u002Fpixie_run.svg?style=social&label=Follow%20%40pixie_run)](https:\u002F\u002Ftwitter.com\u002Fpixie_run)\n[![Mentioned in Awesome Kubernetes](https:\u002F\u002Fawesome.re\u002Fmentioned-badge.svg)](https:\u002F\u002Fgithub.com\u002Framitsurana\u002Fawesome-kubernetes)\n[![Mentioned in Awesome Go](https:\u002F\u002Fawesome.re\u002Fmentioned-badge.svg)](https:\u002F\u002Fgithub.com\u002Favelino\u002Fawesome-go)\n[![Build Status](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Factions\u002Fworkflows\u002Fbuild_and_test.yaml\u002Fbadge.svg?branch=main)](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Factions\u002Fworkflows\u002Fbuild_and_test.yaml)\n[![codecov](https:\u002F\u002Fcodecov.io\u002Fgh\u002Fpixie-io\u002Fpixie\u002Fbranch\u002Fmain\u002Fgraph\u002Fbadge.svg?token=UG7P3QE5PQ)](https:\u002F\u002Fcodecov.io\u002Fgh\u002Fpixie-io\u002Fpixie)\n[![FOSSA Status](https:\u002F\u002Fapp.fossa.com\u002Fapi\u002Fprojects\u002Fcustom%2B26327%2Fgithub.com%2Fpixie-io%2Fpixie.svg?type=shield)](https:\u002F\u002Fapp.fossa.com\u002Fprojects\u002Fcustom%2B26327%2Fgithub.com%2Fpixie-io%2Fpixie?ref=badge_shield)\n[![Artifact HUB](https:\u002F\u002Fimg.shields.io\u002Fendpoint?url=https:\u002F\u002Fartifacthub.io\u002Fbadge\u002Frepository\u002Fpixie-operator)](https:\u002F\u002Fartifacthub.io\u002Fpackages\u002Folm\u002Fcommunity-operators\u002Fpixie-operator)\n[![Go Report Card](https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fpx.dev\u002Fpixie)](https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fpx.dev\u002Fpixie)\n[![CII Best Practices](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F5027\u002Fbadge)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F5027)\n[![CLOMonitor](https:\u002F\u002Fimg.shields.io\u002Fendpoint?url=https:\u002F\u002Fclomonitor.io\u002Fapi\u002Fprojects\u002Fcncf\u002Fpixie\u002Fbadge)](https:\u002F\u002Fclomonitor.io\u002Fprojects\u002Fcncf\u002Fpixie)\n[![OpenSSF Scorecard](https:\u002F\u002Fapi.securityscorecards.dev\u002Fprojects\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Fbadge)](https:\u002F\u002Fapi.securityscorecards.dev\u002Fprojects\u002Fgithub.com\u002Fpixie-io\u002Fpixie)\n\n\u003Cbr>\n\nPixie is an open-source observability tool for Kubernetes applications. Use Pixie to view the high-level state of your cluster (service maps, cluster resources, application traffic) and also drill down into more detailed views (pod state, flame graphs, individual full-body application requests).\n\n## Why Pixie?\n\nThree features enable Pixie's magical developer experience:\n\n- **Auto-telemetry:** Pixie uses eBPF to automatically collect telemetry data such as full-body requests, resource and network metrics, application profiles, and more. See the full list of data sources [here](https:\u002F\u002Fdocs.px.dev\u002Fabout-pixie\u002Fdata-sources\u002F).\n\n- **In-Cluster Edge Compute:** Pixie collects, stores and queries all telemetry data locally in the cluster. Pixie uses less than 5% of cluster CPU and in most cases less than 2%.\n\n- **Scriptability:** [PxL](https:\u002F\u002Fdocs.px.dev\u002Freference\u002Fpxl\u002F), Pixie’s flexible Pythonic query language, can be used across Pixie’s UI, CLI, and client APIs.\n\n## Use Cases\n\n### Network Monitoring\n\n\u003Cimg src=\".readme_assets\u002Fnet_flow_graph.png\" alt=\"Network Flow Graph\" width=\"525\" align=\"right\">\n\n\u003Cbr>\n\nUse Pixie to monitor your network, including:\n\n- The flow of network traffic within your cluster.\n- The flow of DNS requests within your cluster.\n- Individual full-body DNS requests and responses.\n- A Map of TCP drops and TCP retransmits across your cluster.\n\n\u003Cbr>\n\nFor more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fpixie-101\u002Fnetwork-monitoring\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002FqIxzIPBhAUI) an overview.\n\n\u003Cbr clear=\"all\">\n\n### Infrastructure Health\n\n\u003Cimg src=\".readme_assets\u002Fnodes.png\" alt=\"Infrastructure Monitoring\" width=\"525\" align=\"right\">\n\n\u003Cbr>\n\nMonitor your infrastructure alongside your network and application layer, including:\n\n- Resource usage by Pod, Node, Namespace.\n- CPU flame graphs per Pod, Node.\n\n\u003Cbr>\n\nFor more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fpixie-101\u002Finfra-health\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002F2dFIpiBryu8) an overview.\n\n\u003Cbr clear=\"all\">\n\n### Service Performance\n\n\u003Cimg src=\".readme_assets\u002Fservice.png\" alt=\"Service Performance\" width=\"525\" align=\"right\">\n\n\u003Cbr>\n\nPixie automatically traces a [variety of protocols](https:\u002F\u002Fdocs.px.dev\u002Fabout-pixie\u002Fdata-sources\u002F). Get immediate visibility into the health of your services, including:\n\n- The flow of traffic between your services.\n- Latency per service and endpoint.\n- Sample of the slowest requests for an individual service.\n\n\u003Cbr>\n\nFor more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fpixie-101\u002Fservice-performance\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002FRex0yz_5vwc) an overview.\n\n\u003Cbr clear=\"all\">\n\n### Database Query Profiling\n\n\u003Cimg src=\".readme_assets\u002Fsql_query.png\" alt=\"Database Query Profilling\" width=\"525\" align=\"right\">\n\n\u003Cbr>\n\nPixie automatically traces several different [database protocols](https:\u002F\u002Fdocs.px.dev\u002Fabout-pixie\u002Fdata-sources\u002F#supported-protocols). Use Pixie to monitor the performance of your database requests:\n\n- Latency, error, and throughput (LET) rate for all pods.\n- LET rate per normalized query.\n- Latency per individual full-body query.\n- Individual full-body requests and responses.\n\n\u003Cbr>\n\nFor more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fpixie-101\u002Fdatabase-query-profiling\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002F5NkU--hDXRQ) an overview.\n\n\u003Cbr clear=\"all\">\n\n### Request Tracing\n\n\u003Cimg src=\".readme_assets\u002Fhttp_data_filtered.png\" alt=\"Request Tracing\" width=\"525\" align=\"right\">\n\n\u003Cbr>\n\nPixie makes debugging this communication between microservices easy by providing immediate and deep (full-body) visibility into requests flowing through your cluster. See:\n\n- Full-body requests and responses for [supported protocols](https:\u002F\u002Fdocs.px.dev\u002Fabout-pixie\u002Fdata-sources\u002F#supported-protocols).\n- Error rate per Service, Pod.\n\n\u003Cbr>\n\nFor more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fpixie-101\u002Frequest-tracing\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002FGl0so4rbwno) an overview.\n\n\u003Cbr clear=\"all\">\n\n### Continuous Application Profiling\n\n\u003Cimg src=\".readme_assets\u002Fpod_flamegraph.png\" alt=\"Continuous Application Profiling\" width=\"525\" align=\"right\">\n\n\u003Cbr>\n\nUse Pixie's continuous profiling feature to identify performance issues within application code.\n\n\u003Cbr>\n\nFor more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fpixie-101\u002Fprofiler\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002FZr-s3EvAey8) an overview.\n\n\u003Cbr clear=\"all\">\n\n### Distributed bpftrace Deployment\n\nUse Pixie to deploy a [bpftrace](https:\u002F\u002Fgithub.com\u002Fiovisor\u002Fbpftrace) program to all of the nodes in your cluster. After deploying the program, Pixie captures the output into a table and makes the data available to be queried and visualized in the Pixie UI. TCP Drops are pictured. For more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fcustom-data\u002Fdistributed-bpftrace-deployment\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002FxT7OYAgIV28) an overview.\n\n### Dynamic Go Logging\n\nDebug Go binaries deployed in production environments without needing to recompile and redeploy. For more details, check out the [tutorial](https:\u002F\u002Fdocs.px.dev\u002Ftutorials\u002Fcustom-data\u002Fdynamic-go-logging\u002F) or [watch](https:\u002F\u002Fyoutu.be\u002FaH7PHSsiIPM) an overview.\n\n\u003Cbr clear=\"all\">\n\n## Get Started\n\n\u003Cimg src=\".readme_assets\u002Fhttp_data.svg\" alt=\"Request Tracing\" width=\"525\" align=\"right\">\n\nIt takes just a few minutes to install Pixie. To get started, check out the [Install Guides](https:\u002F\u002Fdocs.px.dev\u002Finstalling-pixie\u002Finstall-guides\u002F).\n\n\u003Cbr>\n\nOnce installed, you can interact with Pixie using the:\n\n- [Web-based Live UI](https:\u002F\u002Fdocs.px.dev\u002Fusing-pixie\u002Fusing-live-ui\u002F)\n- [CLI](https:\u002F\u002Fdocs.px.dev\u002Fusing-pixie\u002Fusing-cli\u002F)\n- [API](https:\u002F\u002Fdocs.px.dev\u002Fusing-pixie\u002Fapi-quick-start\u002F)\n\n\u003Cbr clear=\"all\">\n\n## Get Involved\n\nPixie is a community-driven project; we welcome your contribution! For code contributions, please read our [contribution guide](CONTRIBUTING.md).\n\n- File a [GitHub issue](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Fissues) to report a bug or request a feature.\n- Join our [Slack](https:\u002F\u002Fslackin.px.dev) for live conversations and quick questions. We are also available on the [CNCF slack](https:\u002F\u002Fslack.cncf.io\u002Fapp_redirect?channel=pixie\").\n- Follow us on [Twitter](https:\u002F\u002Ftwitter.com\u002Fpixie_run) and [YouTube](https:\u002F\u002Fwww.youtube.com\u002Fchannel\u002FUCOMCDRvBVNIS0lCyOmst7eg).\n- Add our community meeting [calendar](https:\u002F\u002Fcalendar.google.com\u002Fcalendar\u002Fu\u002F0?cid=Y181OTA0Y2ZmNzdhNzdhOGYzMzQxNmNmMjQzODI4ZjY4ZGY5MWMzYzEzZWU3YmQ5NGFjODUzMmRiODg2Y2VjMjkxQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20).\n- Provide feedback on our [roadmap](https:\u002F\u002Fdocs.px.dev\u002Fabout-pixie\u002Froadmap\u002F).\n\n\u003Cbr clear=\"all\">\n\n## Latest Releases\nWe version separate components of Pixie separately, so what Github shows as the \"latest\" release will only be the latest for one of the components.\nWe maintain links to the latest releases for all components here:\n- [CLI v0.8.8](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Freleases\u002Ftag\u002Frelease\u002Fcli\u002Fv0.8.8)\u003C!--cli-latest-release-->\n- [Cloud v0.1.8](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Freleases\u002Ftag\u002Frelease\u002Fcloud\u002Fv0.1.8)\u003C!--cloud-latest-release-->\n- [Vizier v0.14.15](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Freleases\u002Ftag\u002Frelease\u002Fvizier\u002Fv0.14.15)\u003C!--vizier-latest-release-->\n- [Operator v0.1.7](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Freleases\u002Ftag\u002Frelease\u002Foperator\u002Fv0.1.7)\u003C!--operator-latest-release-->\n\n## Changelog\n\nThe changelog is stored in annotated git tags.\n\nFor vizier:\n\n```\ngit for-each-ref refs\u002Ftags\u002Frelease\u002Fvizier\u002F$tagname --format='%(tag) %(contents)'\n```\n\nFor the CLI:\n\n```\ngit for-each-ref refs\u002Ftags\u002Frelease\u002Fcli\u002F$tagname --format='%(tag) %(contents)'\n```\n\nThese are also published on the [releases](https:\u002F\u002Fgithub.com\u002Fpixie-io\u002Fpixie\u002Freleases) page.\n\n## Adopters\n\nThe known adopters and users of Pixie are listed [here](ADOPTERS.md).\n\n## Software Bill of Materials\n\nWe publish a list of all the components Pixie depends on and the corresponding\nversions and licenses [here](https:\u002F\u002Fstorage.googleapis.com\u002Fpixie-dev-public\u002Foss-licenses\u002Flatest.json).\n\n## Acknowledgements\n\nThe Pixie project would like to thank [Equinix Metal](https:\u002F\u002Fwww.equinix.com\u002F) via the [CNCF Community Infrastructure Lab](https:\u002F\u002Fgithub.com\u002Fcncf\u002Fcluster) for graciously providing compute resources to run all the CI\u002FCD for the project.\n\n## About Pixie\n\nPixie was contributed by [New Relic, Inc.](https:\u002F\u002Fnewrelic.com\u002F) to the [Cloud Native Computing Foundation](https:\u002F\u002Fwww.cncf.io\u002F) as a Sandbox project in June 2021.\n\n## License\n\nPixie is licensed under [Apache License, Version 2.0](LICENSE).\n","Pixie 是一个开源的 Kubernetes 应用程序可观测性工具。它利用 eBPF 技术自动收集集群内应用的全量请求、资源和网络指标等数据，并在集群内部进行存储与查询，以极低的资源消耗（通常低于 2% 的 CPU 使用率）提供高效的监控体验。此外，Pixie 支持通过 PxL（一种类似 Python 的脚本语言）来编写自定义查询，增强其灵活性和可扩展性。该工具适用于需要对云原生环境下的服务状态、流量分析及性能瓶颈进行实时监控和深度诊断的各种场景。","2026-06-11 03:25:28","top_topic"]