Create LEM Project Alert (Trigger + Action)

create lem project alert (trigger + action) ui trigger lem > edge lifecycle management > alerts > add action > add trigger a lem alert has two halves that must be created in order the action template (how to notify email, slack, webhook, pagerduty) is created first and returns an id ; the trigger (when to fire metrics threshold or event match) references that id in its actions array step table step name in collection method endpoint body / notes output 1 add action email (or slack / webhook / pagerduty) post {{lem url}}/api/v1/project/action/templates/{{project id}} body shape varies by channel; see saved examples action id (e g bp0pgdjum4l1ltore344h9j1p ) 2 project triggers (optional pre flight) get {{lem url}}/api/v1/project/trigger/definition existing triggers (avoid duplicates) 3 create trigger metrics (or event) post {{lem url}}/api/v1/project/trigger/definition/{{project id}} body must include actions \["\<action id from step 1>"] set sourcetype "metrics" or "events" , scopetype "user" or "project" , deviceid null (all devices) or specific deviceid trigger id 4 (verify) list of incidents get {{lem url}}/api/v1/project/incident/{{project id}} incidents accumulate as triggers fire incident list with severity, timestamp, action result cleanup operation endpoint delete action delete /api/v1/project/action/templates/{{project id}}/{{alert id}} delete trigger delete /api/v1/project/trigger/definition/{{project id}}/{{trigger id}} project alerts vs instance alerts this chain creates project scoped alerts that notify project members about edge metric/event conditions for lem instance level alerts (notify ops about lem itself), use the parallel chain at /admin/v1/instance alert/trigger/ and /admin/v1/instance alert/action/templates/