Skip to main content

Synopsis

Report a snapshot of artifacts running in specific filesystem paths to Kosli.
You can report directory or file artifacts in one or more filesystem paths. Artifacts names and the paths to include and exclude when fingerprinting them can be defined in a paths file which can be provided using --paths-file.
Paths files can be in YAML, JSON or TOML formats. They specify a list of artifacts to fingerprint. For each artifact, the file specifies a base path to look for the artifact in and (optionally) a list of paths to exclude. Excluded paths are relative to the artifact path(s) and can be literal paths or glob patterns.
The supported glob pattern syntax is documented here: https://pkg.go.dev/path/filepath#Match , plus the ability to use recursive globs ”**”
To specify paths in a directory artifact that should always be excluded from the SHA256 calculation, you can add a .kosli_ignore file to the root of the artifact. Each line should specify a relative path or path glob to be ignored. You can include comments in this file, using #. The .kosli_ignore will be treated as part of the artifact like any other file, unless it is explicitly ignored itself. This is an example YAML paths spec file:

Flags

Flags inherited from parent commands

Examples Use Cases

These examples all assume that the flags --api-token, --org, --host, (and --flow, --trail when required), are set/provided.
Last modified on July 21, 2026