Fiberplane CLI ⌨️

A command line tool for interacting with Fiberplane.

Usage

Login

Before running most commands, you'll need to authorize the CLI to act on your behalf.

fp login

This will open a web browser and take you through the Google OAuth flow.

FPD

The Fiberplane Daemon enables Fiberplane to connect to your organization's data sources (e.g. Prometheus) without exposing them to the public internet.

Add a daemon

fp daemon add my-first-proxy

This will register a daemon with the name my-first-daemon and return the FPD Auth Token you will run the daemon with.

You can use any name for your daemon. Organizations may have multiple daemons for different Kubernetes clusters or environments (production, staging, etc). We would recommend giving each one a name that corresponds to the environment it will be running in on your infrastructure.

Managing FPD instances

The CLI offers other commands to help view and manage your organization's daemons:

• fp daemon list - shows your daemons' names, IDs, and connection statuses
• fp daemon data-sources - shows the data sources exposed by all of your daemons
• fp daemon get <daemon_id> - shows detailed information about a specific daemon
• fp daemon delete <daemon_id> - delete the given daemon

Templates

Templates enable you to programmatically generate Fiberplane notebooks to run repeatable workflows.

You can browse our example templates to see templates for use cases such as incident response and root cause analyses.

Creating Templates

Generate a template from an existing notebook with the convert command:

fp templates convert https://studio.fiberplane.com/notebook/My-Notebook-<NOTEBOOK_ID_HERE>

Alternatively, you can create a blank template with the init command:

fp templates init

See the template API documentation for all of the methods available in the template library.

Using Templates to Create Notebooks

You can manually create a notebook from a template using the expand command:

fp templates expand <TEMPLATE_ID>
fp templates expand ./path/to/template.jsonnet

Passing Template Arguments

Most templates export a top-level function so that certain notebook details can be filled in at the time the notebook is created from the template.

You can pass function arguments via the CLI as simple key-value pairs: fp templates expand <TEMPLATE_ID> arg1=value1,arg2=value2 or as a JSON object: fp templates expand <TEMPLATE_ID> {"arg1":"value1","arg2":"value2"}.

Triggers

Triggers enable you to create Fiberplane Notebooks from Templates via an API call. This can be used to automatically create notebooks from alerts.

Creating Triggers

You can create a Trigger from a local template:

fp triggers create --template-id <TEMPLATE_ID>

This command returns the trigger URL used to invoke the trigger (see the next section).

Invoking Triggers

Normally, Triggers are invoked with HTTP POST requests to https://studio.fiberplane.com/api/triggers/:id/:secret_key. The Trigger's URL is printed when it is created via the CLI.

The CLI can be used to test out a trigger:

fp triggers invoke <TRIGGER_ID> <SECRET_KEY> arg1=value1,arg2=value2

Managing Triggers

The CLI also supports the following operations for your (organization's) triggers:

• fp triggers list
• fp triggers get <id>
• fp triggers delete <id>

Front Matter Collections

The CLI allows to manage the front matter collections of a workspace, so that common front matter fields can easily be grouped for integration in notebooks. The subcommand for these is fp front-matter-collections, which can be shortened to fp fmc. Check fp fmc help to see all the available subcommands

Creating a front matter collection

All the parameters that are not specified in the command line will be prompted by the CLI when creating a front matter collection.

fp fmc create path/to/schema.json

An example of the format of the expected JSON (it follows the API format from the common models of fiberplane):

[
    {
        "key": "incident.commander",
        "schema": {
            "type": "user",
            "displayName": "Commander"
        }
    },
    {
        "key": "incident.status",
        "schema": {
            "type": "string",
            "displayName": "Status",
            "options": [
                {"value": "started"},
                {"value": "detected"},
                {"value": "root cause found"},
                {"value": "patch applied"},
                {"value": "resolved"}
            ]
        }
    },
    {
        "key": "incident.ebit-loss",
        "schema": {
            "type": "number",
            "displayName": "EBIT loss",
            "suffix": "EUR"
        }
    },
    {
        "key": "incident.affected-slos",
        "schema": {
            "type": "string",
            "displayName": "Affected SLOs",
            "multiple": true,
            "allowExtraValues": true,
            "options": [
                {"value": "API latency"},
                {"value": "Payment success rate"}
            ]
        }
    }
]

Fetching a front matter collection

A good way to modify a front matter collection is to fetch the current version to modify only the relevant fields in the received JSON. The way to get a front matter collection is to use the get subcommand:

fp fmc get

Just as all other commands within fp, the CLI will prompt you for all the missing informations to complete the query.

Notebooks

The CLI allows for management for management of your notebooks. Currently the following commands are supported:

• fp notebooks add
• fp notebooks get <id>
• fp notebooks front-matter ...

Creating a new notebook

The fp cli is able to create a notebook. You can specify a couple of parameters through arguments and then the cli will create a notebook for you.

fp notebooks add --title "test" --label key=value

Retrieving a notebook

It is also possible to retrieve the notebook and display it as JSON.

fp notebooks get <notebook_id>

Manipulating front matter

It is possible to manipulate the front matter of notebooks programmatically using the front-matter subcommand of notebook. Check all the options out using:

fp notebooks front-matter help

Examples include:

# Edit a front matter entry in an existing notebook
fp notebook front-matter edit --front-matter-key severity --new-value info
# Append the "incident" collection to an existing notebook
fp nb fm add-collection --name incident

Getting Help

Please see COMMUNITY.md for ways to reach out to us.

Contributing

See CONTRIBUTING.md.

Code of Conduct

See CODE_OF_CONDUCT.md.

License

Our providers and the PDK are distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT.