Fiberplane Studio is available for the Web.
To get started go to https://fiberplane.com/ and log in with your Fiberplane account (currently available only for Google Workspace or Gmail users). You can also get right to your notebook by typing fp.new
Fiberplane Studio allows you to query, visualize, and understand metrics and logs in your infrastructure.
Whenever you execute a query in the notebook:
- The query is forwarded to the Fiberplane
fpdin your cluster;
fpdthen queries the Provider data source (e.g. your Prometheus or Elastic instance);
- When the Provider returns the data, the
fpdprocesses, encrypts, and then returns it back to the Studio.
The Fiberplane Daemon is a package that runs in your infrastructure. It enables you to connect the Fiberplane Studio to data sources in your cluster(s) securely without exposing them to the Internet.
The Fiberplane Daemon is available as a container on Docker Hub.
In order for the Daemon to receive queries from Fiberplane Notebooks, it needs to be authorized. This step will generate a Daemon API Token that will be needed in later steps.
You can do it in the Settings > FPD menu or using our CLI tool.
In order for the Daemon to talk to the Fiberplane Studio successfully it needs to be successfully authorized. This step will generate a Daemon API Token that will be needed later.
- Go to your Fiberplane Settings page.
+ Newto register a proxy with a name that identifies the cluster you will install it into (for example, "Production"). This will generate and display a Daemon API Token that the proxy will use to authenticate with the Fiberplane Studio.
- Copy the Daemon API Token generated in Step 2 for the next step.
Download and install the Fiberplane CLI
curl --proto '=https' --tlsv1.2 -sSf https://fp.dev/install.sh | sh
Or download the Fiberplane CLI manually (make sure to make it executable
chmod +x ./fp):
Authenticate your CLI with Fiberplane
To register a daemon run a command
fp daemon create:
$ fp daemon create my-daemon-name
Token <YOUR_DAEMON_API_TOKEN> <-- SAVE THIS FOR LATER!
You can leave out the daemon name to have one randomly generated, but we
recommend naming it according to the environment it will be deployed to (for
production). Note that daemon names must follow the Fiberplane name
You can now:
- add Providers;
- deploy the
fpdto Kubernetes cluster, Docker container or run it locally for testing.
Updated 12 months ago