pixie icon indicating copy to clipboard operation
pixie copied to clipboard

Instant Kubernetes-Native Application Observability

Results 408 pixie issues
Sort by recently updated
recently updated
newest added

A user reported on pixie community slack channel, that ErrorResponse message were not exported into pgsql_events table. I confirmed the issue with stirling_wrapper. Need to make sure ErrorResponse is output...

priority/backlog
triage/accepted
tmp/imported

Error: Failed to execute script error=Failed to execute script: rpc error: code = Unknown desc = error in ForwardQueryResult: Query 7490b68d-af25-4850-a981-8967bf906241 can not accept more data, consumer likely died ```...

priority/backlog
triage/accepted
tmp/imported

See example script, we never see any cluster IP or external IP even though we should import px 1. Use this scratch pad to write and run one-off scripts. 1....

priority/backlog
triage/accepted
tmp/imported

Repro instructions * Go to px/namespace (namespace 'pl') * Change 'pl' to 'default' quickly (and press enter right away) * Note that due to the slow processing, only part of...

priority/backlog
triage/accepted
tmp/imported

In the distributed planner, inside the stitcher, there is a check for whether an Op has to run on PEM or not. Currently, that check just checks if the op...

priority/backlog
triage/accepted
tmp/imported

Users would like to see a visualization of individual traces from their services. For now, these traces will be determined based on a user supplied trace-id header. In addition, we...

priority/backlog
triage/accepted
tmp/imported

In our current state, when a user deploys Pixie, the operator generates TLS certs that are valid for 1 year. However, after the year is over, the TLS certs will...

priority/backlog
triage/accepted
tmp/imported

Existing code does not support all message types of PGSQL, because of lack of time. The behavior, however, just errors out when encounter unrecognized message types. That is wrong. As...

priority/backlog
triage/accepted
tmp/imported

Stirling now supports gRPC decompression. However, during a brief testing on gke:prod cluster, gunzip failures were identified through the relevant log lines in the code. One possible culprit is that...

priority/backlog
triage/accepted
tmp/imported

To reproduce the error, deploy a cluster and then log onto a node that has a pem, and then kill the pem: ``` gcloud compute ssh sudo kill $(pidof pem)...

priority/backlog
triage/accepted
tmp/imported