Dashboard fatigue is one of key reasons for poor adoption of logging tools among developers. With pb, we intend to bring the familiar command line interface for querying and analyzing log data at scale.
pb is the command line interface for Parseable Server. pb allows you to manage Streams, Users, and Data on Parseable Server. You can use pb to manage multiple Parseable Server instances using Profiles.
pb is available as a single, self contained binary for Mac, Linux, and Windows. You can download the latest version from the releases page.
To install pb, download the binary for your platform, un-tar the binary and place it in your $PATH.
pb is configured with demo profile as the default. This means you can directly start using pb against the demo Parseable Server.
To start using pb against your Parseable server, create a profile (a profile is a set of credentials for a Parseable Server instance). You can create a profile using the pb profile add command. For example:
pb profile add local http://localhost:8000 admin adminThis will create a profile named local that points to the Parseable Server at http://localhost:8000 and uses the username admin and password admin.
You can create as many profiles as you like. To avoid having to specify the profile name every time you run a command, pb allows setting a default profile. To set the default profile, use the pb profile default command. For example:
pb profile default localBy default pb sends json data to stdout.
pb query run "select * from backend" --from=1m --to=nowor specifying time range in rfc3999
pb query run "select * from backend" --from=2024-01-00T01:40:00.000Z --to=2024-01-00T01:55:00.000ZYou can use tools like jq and grep to further process and filter the output. Some examples:
pb query run "select * from backend" --from=1m --to=now | jq . pb query run "select host, id, method, status from backend where status = 500" --from=1m --to=now | jq . > 500.json pb query run "select host, id, method, status from backend where status = 500" | jq '. | select(.method == "PATCH")' pb query run "select host, id, method, status from backend where status = 500" --from=1m --to=now | grep "POST" | jq . | lessTo save a query as a filter use the --save-as flag followed by a name for the filter. For example:
pb query run "select * from backend" --from=1m --to=now --save-as=FilterNameTo list all filter for the active user run:
pb query listpb can be used to tail live data from Parseable Server. To tail live data, use the pb tail command. For example:
pb tail backendYou can also use the terminal tools like jq and grep to filter and process the tail output. Some examples:
pb tail backend | jq '. | select(.method == "PATCH")' pb tail backend | grep "POST" | jq .To stop tailing, press Ctrl+C.
Once a profile is configured, you can use pb to query and manage that Parseable Server instance. For example, to list all the streams on the server, run:
pb stream listTo list all the users with their privileges, run:
pb user listYou can also use the pb users command to manage users.
Version command prints the version of pb and the Parseable Server it is configured to use.
pb versionTo enable autocomplete for pb, run the following command according to your shell:
For bash:
pb autocomplete bash > /etc/bash_completion.d/pb source /etc/bash_completion.d/pbFor zsh:
pb autocomplete zsh > /usr/local/share/zsh/site-functions/_pb autoload -U compinit && compinitFor powershell
pb autocomplete powershell > $env:USERPROFILE\Documents\PowerShell\pb_complete.ps1 . $PROFILE