Changes for page Cleanup Alerting in Manage

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -14,27 +14,30 @@
14	14
15	15	=== 3.1 Scenario's when to cleanup the Alerting phase ===
16	16
17		-* A user is no longer active on the integration model. The use may still be referenced in the notification settings and should be removed
	17	+* A user is no longer active on the integration model.
	18	+ ** The user may still be referenced in the notification settings and should be removed
18	18	* A specific runtime is removed from the integration model that is referenced in the Alerting
19	19	* A flow or integration is removed from the integration model that is reference in the Alerting
20	20
21	21	=== 3.1 Steps to clean ===
22	22
23		-Navigate to the Triggers first.
	24	+Once you have opened your model you should navigate to the Manage environment. From here you should open the Alerting section under Manage and select Triggers. Here you can change the relevant triggers.
24	24
25		-* Locate Queue specific
26		- If you have configured the alerting following the best practice outlined in the user guide for Alerting, the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
	26	+**Queue specific**
27	27
28		- ** Standard – Queue consumers too high
29		- ** Standard – Queue consumers too low
	28	+If you have configured the alerting following the best practice outlined in the user guide for Alerting, the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
30	30
31		-* Locate Runtime specific
32		- If you are removing the last flow belonging to a system and you have followed the best practice outlined here the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
	30	+* Standard – Queue consumers too high
	31	+* Standard – Queue consumers too low
33	33
34		- ** Standard – Data measurements missing
35		- ** Standard – Log entries missing
36		- ** Standard – Error log entry
	33	+**Runtime specific**
37	37
	35	+If you are removing the last flow belonging to a system and you have followed the best practice outlined here the following triggers (at least!!!) need to be changed. For your specific situation more triggers could be relevant
	36	+
	37	+* Standard – Data measurements missing
	38	+* Standard – Log entries missing
	39	+* Standard – Error log entry
	40	+
38	38	* Once you have located the candidates, update and/or remove the triggers relevant for update
39	39	* Review if you need to remove a notification setting in case a trigger is removed. If yes, remove it.
40	40	* Review if you need to remove a tag in case the tag is not used in any trigger. If yes, remove it.