Download AppScope, then explore its CLI. Getting started is that easy.
You can download AppScope as a binary in your Linux OS, or as a container.
Review the AppScope Requirements to ensure that you’re completing these steps on a supported system.
Then, from Cribl's download page, download the binary and follow the instructions there.
Or, you can use these CLI commands to directly download the binary and make it executable:
LATEST=$(curl -Ls https://cdn.cribl.io/dl/scope/latest) curl -Lo scope https://cdn.cribl.io/dl/scope/$LATEST/linux/$(uname -m)/scope curl -Ls https://cdn.cribl.io/dl/scope/$LATEST/linux/$(uname -m)/scope.md5 | md5sum -c chmod +x scope
You're ready to start working with AppScope.
Before you start, though, you may want to consider where to run AppScope from.
From Cribl's download page, you can also download AppScope's most recently tagged Ubuntu container.
This will link you to the AppScope repo on Docker Hub, which provides instructions and access to earlier builds.
Each container provides the AppScope binary on Ubuntu 20.04.
Run some scope commands:
scope run ps -ef scope events scope metrics
Now you are ready to explore the CLI:
scope -hto view CLI options.
If an application crashes when scoped, you can set the
SCOPE_ERROR_SIGNAL_HANDLER environment variable to
true to turn on backtrace logging. This should provide more informative logs if crashes recur. Feel free to contact the AppScope team and/or open a new issue if this happens.
Where AppScope lives on your system is up to you. To decide wisely, first consider which of the two ways of working with AppScope fit your situation: ad hoc or planned-out.
For ad hoc exploration and investigation, one choice that follows standard practice for an "add-on software package" is to locate AppScope in
/opt. Since in the AppScope context,
scope is a command, it helps to call the directory where AppScope lives something other than
scope. For example, you can name the directory
/opt/appscope, to make it clear that
/opt/appscope/scope is the
Cribl does not recommend running AppScope from any user's home directory, because that leads to file ownership and permissions problems if additional users try to run AppScope.
By default, the AppScope CLI will output data to the local filesystem where it's running. While this can work fine for "ad hoc" investigations, it can cause problems for longer-duration scenarios like application monitoring, where the local filesystem may not have room for the data being written.
Also consider what level of logging you want from AppScope, and where those logs should go. In planned-out scenarios, where AppScope runs persistently (including as a service), configuring logging judiciously can prevent AppScope from using up too much disk space.
To customize AppScope's data-writing and logging, edit the
scope.yml config file.