The Sentinel CLI (sentinel) is a .NET global tool for authenticating, querying logs, managing alerts, inspecting incidents, and listing tenants from the command line.
dotnet pack cli/Sentinel.CLI/Sentinel.CLI.csproj -c Release
dotnet tool install --global --add-source cli/Sentinel.CLI/bin/Release sentineldotnet run --project cli/Sentinel.CLI -- --help| Option | Default | Description |
|---|---|---|
--base-url |
http://localhost:5018 |
Sentinel API base URL |
--output |
json |
Output format: json or yaml |
Authenticate and persist credentials to ~/.sentinel/config.json:
sentinel auth login --email user@example.com --password secret --tenant-id <guid>With YAML output:
sentinel auth login --email user@example.com --password secret --output yamlSubsequent commands read the stored access token, refresh token, and tenant ID automatically.
sentinel logs search --query "error" --level error --service api --limit 50Supported filters:
--query— full-text search--level— log level--service— service name--environment— deployment environment--from/--to— ISO 8601 timestamps--limit/--offset— pagination
sentinel alerts list
sentinel alerts list --output yamlsentinel incidents show <incident-id>sentinel tenants listsentinel tenants list --output jsonsentinel logs search --query timeout --output yamlAfter auth login, credentials are stored at:
~/.sentinel/config.json
Example structure:
{
"baseUrl": "http://localhost:5018",
"accessToken": "<jwt>",
"refreshToken": "<refresh>",
"tenantId": "<guid>",
"email": "user@example.com"
}Use --base-url to target a different Sentinel deployment without editing the config file:
sentinel --base-url https://sentinel.example.com tenants list0— success1— API or validation error (error details written to stdout in the selected output format)
- SDK Guide — programmatic access with .NET, Node, Go, and Python SDKs
- Architecture — platform overview