Charlie
06/02/2026, 12:45 PMkapa.ai
06/02/2026, 12:45 PM--env flag accepts only dev or prod as valid values â custom values like prod-us or UAT are not supported. [CLI options]
However, there is an important limitation: the --env flag does not currently affect the content of individual Slack alerts sent by edr monitor. It only influences:
1. edr report â shows the environment in the top right of the report.
2. edr send-report â includes the environment in the summary title sent to Slack. [env flag behavior]
A bug was previously reported where the --env flag was not visible in Teams/Slack alerts even though it appeared in the report. This was acknowledged and fixed in a subsequent release. [bug fix]
Workarounds for environment visibility in alerts Since --env is limited to `dev`/`prod` and doesn't enrich individual alert messages, a common community approach is to use separate Slack channels per environment (e.g., data-alerts-prod vs data-alerts-dev), which makes the environment immediately obvious without expanding the alert. [community approach]
If you need a custom environment label (e.g., prod-us), you can use the --project-name flag as a workaround:
edr monitor --project-name "MyProject (prod-us)" --slack-token <token> --slack-channel-name <channel>
[project-name workaround] đ 0 button đ 0 button âšī¸ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.Charlie
06/02/2026, 1:33 PM