> ## Documentation Index
> Fetch the complete documentation index at: https://opensre.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Bash
> Using Tracer with Bash scripts
Tracer can monitor any Bash-based pipeline, from small scripts to large chained commands, giving instant visibility into each command’s behavior.
## Why use Tracer in combination with Bash
Many scientific or data pipelines rely on simple shell scripts that lack structured logging.
Tracer automatically adds observability:
* Traces every subprocess (even background jobs)
* Captures CPU, memory, and I/O usage for each command
* Provides a single timeline of all steps
* Enables root-cause debugging for failures or stalls
* Works for scripts, loops, and complex shell pipelines
## Getting started
### Prerequisites
* Bash 4.0 or higher
* Tracer installed on [your operating system](/environments/overview)
### Just run your pipeline, Tracer will automatically attach
If Tracer is already installed on your operating system, you only need to enable the Tracer agent for pipelines that have not been run with Tracer before.
In that case, run the following command:
```bash theme={null}
sudo tracer init --token
```
Go to our [onboarding](https://app.tracer.cloud/dashboard) to get your own personal token
When running this command, you will be asked to name your pipeline for clear labeling in the dashboard.
## Examples
Run a Bash script under Tracer:
```bash theme={null}
bash my_analysis.sh
```
or launch the Tracer demo workflow:
```bash theme={null}
sudo tracer demo
```
Once the pipeline starts, open the Tracer dashboard, and you’ll see each command as a timeline step updating in real time.
Watch your pipeline run in the Tracer dashboard
View real-time metrics, resource usage, and performance insights for your pipeline runs.
