pixie-io/pxapi.go

pxapi.go is a Go API client for interacting with Pixie, a no-instrumentation Kubernetes observability platform.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

pixie-io/pxapi.go has 10+ stars on GitHub, is written in Go, and was last pushed on Apr 24, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 30 minutes ago
Added to GitGenius on October 15th, 2026
Created on April 19th, 2021
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 3
Total Stargazers: 14 (+0)
Total Subscribers: 1 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

pxapi.go is a Go API client for interacting with Pixie, a no-instrumentation Kubernetes observability platform.

The tool solves the problem of programmatically accessing observability data from Kubernetes clusters without requiring application instrumentation. It provides a Go interface to Pixie's query and data retrieval capabilities, allowing developers to build custom integrations and automation on top of Pixie's eBPF-based monitoring infrastructure.

Developers should choose this tool if they are building Go applications that need to query or consume observability data from Pixie deployments. It suits projects that require programmatic access to metrics, traces, or logs from Kubernetes environments and want to avoid writing direct HTTP clients against Pixie's underlying APIs. The tool is most valuable for teams already using Pixie who need to integrate its data into their own systems or build custom dashboards and alerting logic.

The project is published from a primary repository using an automated mirroring process, which means contributions and issues should be directed to the main Pixie repository rather than this one. This structure indicates the Go API is maintained as part of a larger platform effort rather than as an independent project, with changes flowing through a centralized development workflow.