Footprints

A Footprint is a record of a test execution in Tosca or Tosca Cloud. If you've connected Tosca to SeaLights, you can configure the ABAP Agent to collect Footprints data. When you run a test in Tosca, the Agent matches the executable ABAP components you ran against objects in the latest Build Modification. The agent sends this data to SeaLights in a Footprint.

Collect Footprint data

The footprints run command lets you collect Footprint data for a Pipeline.

Syntax

slabapcli.exe footprints run --pipeline <pipeline-name>

Parameter

Required

Description

--pipeline

Yes

The Pipeline name (as shown in pipeline list).

Example

Command

slabapcli.exe footprints run --pipeline "HH_SLABAPCLI_170625"

Expected output (PowerShell)

.\slabapcli.exe footprints run --pipeline 'HH_SLABAPCLI_170625'
[2025-06-18 15:07:58.337+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[2025-06-18 15:07:58.337+01:00] [info] Config pathname: ../config/config.toml
[2025-06-18 15:07:58.341+01:00] [info] resource = footprints. command = run
[2025-06-18 15:07:58.341+01:00] [info] pipline: HH_SLABAPCLI_170625
[2025-06-18 15:07:58.370+01:00] [info] Run scheduled daily. interval = 5m. duration = 1d
[2025-06-18 15:07:58.370+01:00] [info] Total time: 00:00:00.033

Filter Footprint data

You can exclude specific SCMON context objects from footprints collection using the typequeries field in the [footprints] section of config.toml. This is useful if you want to filter out standard SAP programs, transactions, or function modules that aren't relevant to your testing.

See Configuration settings — Footprints type queries for syntax and examples.

TODO (from v1.5 draft): Confirm the link target for "Configuration settings — Footprints type queries" once that page exists in the v1.5 section.

Stop Footprint data collection

The footprints stop command stops the collection of Footprint data for a Pipeline. When you stop or replace a Footprints task, the Agent automatically stops any watcher process for that task.