We are using a custom probe (email2alarm) to read Gmail inbox and convert to an alarm.
As per my observation, the 'email2alarm' probe has generated the 'Alarm ID' but it was not converted to an alarm.
Need your help to investigate, why the nas probe has no alert triggered in the console.
email2alarm log (few lines) (server time UTC zone):
Dec 09 10:34:38:552 [Thread-11711, e2a-cd-pipeline] Critical Notification
Dec 09 10:34:38:553 [Thread-11711, e2a-cd-pipeline] Alarm raised with ID :: SK43987936-46511
Dec 09 10:34:38:553 [Thread-11711, e2a-cd-pipeline] FAILURE: Job '<jobname> - Build #[14583]' ::
Job '<jobname> Build #[14583]' - [FAILURE!]!^M
Namespace validation failed. Cannot run the pipeline for team <team_name>.
Dec 09 10:34:38:553 [Thread-11711, e2a-cd-pipeline] Reading subject: FAILURE: Job '<job_name> - Build #[14583]'
Dec 09 10:34:38:553 [Thread-11711, e2a-cd-pipeline] Reading message body:
Job 'dockcp/pipeline-test-gpus1/pipeline_compose with Build #[14583]' - [FAILURE!]!^M