user avatar
PC-940 Fix topbar when showing deployInstructions
Michelle Nguyen authored
Summary: Currently when a user has no clusters and we should the deploy instructions, the topbar is rendered in a weird position rather than the top of the page.

Test Plan: yarn dev

Reviewers: vihang, philkuz, zasgar

Reviewed By: vihang

JIRA Issues: PC-940

Differential Revision: https://phab.corp.pixielabs.ai/D8689

GitOrigin-RevId: bbb7be76af5a53ba6b2ab2c31aea6726ebb626bf
10db4283
Name Last commit Last update
.github Add github issue templates
.idea PP-2609 - Change references from px.dev/pixielabs -> px.dev/pixie
.readme_assets PP-2627 - Update front page readme
.vscode Create new breadcrumbs component to use new script context
bazel Add special resolution for UI resources to branch between public and private Pixie Cloud
ci Fixup Jenkins + Buildbuddy and remote cache interaction
demos Fix demo apps prod upload bucket
k8s Make hydra client job wait for hydra
scripts Fix update_ts_protos.js to copy GRPC client
skaffold PP-2630 Update cloud/vizier images to be public
src PC-940 Fix topbar when showing deployInstructions
styleguide Update styleguide to add code specific information
third_party Restore cpplint to updated version
tools PC-937 - Update node to v16
.arcconfig Move linters into tools
.arclint Trace sock_alloc() and use its return variable to extract remote address and port
.arcunit Rewrite generated file checker tests
.bazel_fix_commands.json Adding ibazel fix commands
.bazelignore Move chef under tools
.bazelproject Clion with bazel setup
.bazelrc Add extension to get_workspace_status.
.clang-format Clang-format: Make pointer bind to type
.clang-tidy Silence some more clang-tidy rules that we never seem to follow
.flake8rc Adding scripts that grab bazel licenses
.gitattributes Add github attribute for PxL
.gitignore
.gitmodules
.golangci.yaml
.graphqlconfig
.pxl.flake8rc
.snyk
.yamllint
AUTHORS
BUILD.bazel
CLA.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md
DEVELOPMENT.md
Doxyfile
GOVERNANCE.md
Jenkinsfile
LICENSE
Makefile
README.md
WORKSPACE
codecov.yml
docker.properties
go.mod
go.sum
go_deps.bzl
pixielabs.sublime-project
prototool.yaml
workspace.bzl

Pixie!


Docs Slack Mentioned in Awesome Kubernetes Mentioned in Awesome Go Build Status codecov


What is Pixie?

Pixie

Pixie gives you instant visibility by giving access to metrics, events, traces and logs without changing code.

Try our community beta and join our community on slack.


Table of contents

Quick Start

Review Pixie's requirements to make sure that your Kubernetes cluster is supported.

Signup

Visit our product page and signup with your google account.

Install CLI

Run the command below:

bash -c "$(curl -fsSL https://withpixie.ai/install.sh)"

Or see our Installation Docs to install Pixie using Docker, Debian, RPM or with the latest binary.

(optional) Setup a sandbox

If you don't already have a K8s cluster available, you can use Minikube to set-up a local environment:

  • On Linux, run minikube start --cpus=4 --memory=6000 --driver=kvm2 -p=<cluster-name>. The default docker driver is not currently supported, so using the kvm2 driver is important.

  • On Mac, run minikube start --cpus=4 --memory=6000 -p=<cluster-name>.

More detailed instructions are available here.

Start a demo-app:

🚀 Deploy Pixie

Use the CLI to deploy the Pixie Platform in your K8s cluster by running:

px deploy

Alternatively, you can deploy with YAML or Helm.


Check out our install guides and walkthrough videos for alternate install schemes.

Get Instant Auto-Telemetry

Run scripts with px CLI

CLI Demo


Service SLA:

px run px/service_stats


Node health:

px run px/node_stats


MySQL metrics:

px run px/mysql_stats


Explore more scripts by running:

px scripts list


Check out our pxl_scripts folder for more examples.


View machine generated dashboards with Live views

CLI Demo

The Pixie Platform auto-generates "Live View" dashboard to visualize script results.

You can view them by clicking on the URLs prompted by px or by visiting:

https://work.withpixie.ai/live


Pipe Pixie dust into any tool

CLI Demo

You can transform and pipe your script results into any other system or workflow by consuming px results with tools like jq.

Example with http_data:

px run px/http_data -o json| jq -r .

More examples here


To see more script examples and learn how to write your own, check out our docs for more guides


Contributing

Refer to our contribution guide!

Under the Hood

Three fundamental innovations enable Pixie's magical developer experience:

Progressive Instrumentation: Pixie Edge Modules (“PEMs”) collect full body request traces (via eBPF), system metrics & K8s events without the need for code-changes and at less than 5% overhead. Custom metrics, traces & logs can be integrated into the Pixie Command Module.

In-Cluster Edge Compute: The Pixie Command Module is deployed in your K8s cluster to isolate data storage and computation within your environment for drastically better intelligence, performance & security.

Command Driven Interfaces: Programmatically access data via the Pixie CLI and Pixie UI which are designed ground-up to allow you to run analysis & debug scenarios faster than any other developer tool.

For more information on Pixie Platform's architecture, check out our docs or overview deck

Resources

About Us

Pixie was started by a San Francisco based startup, Pixie Labs Inc. Our north star is to build a new generation of intelligent products which empower developers to engineer the future. We were acquired by New Relic in 2020.

New Relic, Inc. open sourced Pixie in April 2021.

License

Pixie is licensed under Apache License, Version 2.0.