bcgov/Sysdig Monitor

Create/update Sysdig email alerts for an OpenShift app on PROD deploy

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit May 29, 2026
License: Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: bcgov/action-sysdig-monitor@122c7672e37f97cf27c1b17d1c0738f152b1bcf7 # 0.0.2

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
sysdig_api_token	Sysdig API token, scoped to the project's Sysdig team. Should be stored as a GitHub secret (SYSDIG_API_TOKEN). If empty/unset the action will log a warning and exit 0 — it never blocks the deploy.	no	""
oc_namespace	Prod OpenShift namespace. Example: abc123-prod	yes	—
app	Application name. Used to namespace alert + channel names so teams running many apps can scan their Sysdig alert list. Example: nr-rept	yes	—
alerts_dir	Path (relative to the consuming repo's checkout) to a directory containing alert template *.json files. Each file is upserted as an alert per component. Filename (without .json) becomes the alert-name suffix (e.g. crashloop.json -> <app>-<component>-crashloop). Add or remove files in this directory to extend or trim the alert set. The action never deletes Sysdig alerts when files are removed — clean those up in the Sysdig UI if needed.	—	monitoring/alerts
components	Comma-separated list of Deployment names to monitor. Each component gets one alert per file in alerts_dir. Example: frontend,backend	—	frontend,backend
alert_duration_minutes	Minutes a condition must hold before an alert fires. Acts as the debounce that absorbs rolling-deploy noise.	—	5
sysdig_api_url	Sysdig SaaS API base URL. Override only if BC Gov migrates to a different tenancy.	—	https://app.sysdigcloud.com
debug	Enable verbose logging (prints API requests/responses).	—	false

Outputs

no outputs