Tetragon: trace file opens with a policy
Trace file opens with a policy.
1. Run the example
Download the Tetragon example. Extract it, install httpx, set your API URL and token, then run python client.py. The client uploads the included inputs, submits the command, and saves the result under results/RUN_ID.
2. Check the result
Read events.jsonl for the selected kernel events and tetragon.log for collector diagnostics.
Read the native exit code and cleanup status printed by the client. Read results and save reports explains the returned files.
3. Use your own inputs
Edit example.json to change the command arguments, requested outputs or deadline. Replace the files under inputs/ with your own data, keeping the staged paths aligned with the command. The client creates the artifact IDs for you; illustrative IDs shown here must not be copied into a live request.
Files used by this example
run.pypolicy.yaml
The example uses supplied files or the disposable execution environment. Nothing from the environment carries into a later run unless you request and reuse its output.
Commands, version and prerequisites
Qualified version: 1.8.0. Commands: tetragon, tetra, python.
- Standalone Tetragon inside a fresh isolated Linux VM. Supply tracing policies; events describe this guest. No host kernel access is exposed.
Inspect GET /v1/tools/tetragon for the current installed version and readiness. The published snapshot has 2 functional case(s), plus timeout and cancellation checks. These examples demonstrate the native path; other flags and inputs are supported within the tool’s runtime limits.