Threshold Setting

Issues	Cause	Diagnosis	Resolution
Threshold values have exceeded the set limits, and the end user has not been notified.	The abpm.diagnostics.notification.receiver.email property is set to blank by default, meaning no email addresses are specified to receive notifications.	Verify if the abpm.diagnostics.notification.receiver.email property is set in the system properties.	Set the abpm.diagnostics.notification.receiver.email property. Email ID(s) mentioned here will receive notifications when a component's threshold reaches its specified limit. Separate multiple email IDs by a comma. It is recommended to set the email IDs separated by commas to receive the notification when threshold values are reached.
abpm.diagnostics.notification.receiver.email property left blank that will cause an issue.	If the property is left blank, the system will not initiate a check, and no notification is sent to the email ID(s) mentioned in the abpm.diagnostics.notification.receiver.email property.	Check the system properties to see if the abpm.diagnostics.failure.notification.interval property is left blank.	Set the abpm.diagnostics.failure.notification.interval property to a time interval (in minutes) when the system triggers a check for each component reaching its threshold.
abpm.diagnostics.license.threshold	1.License Exceedance: The threshold is depends on number of active users or the amount of concurrent processing capacity allowed under the current license. 2.Monitoring Configuration: Misconfiguration of the license monitoring thresholds or alerts within Adeptia ABPM.	Configure the system to send license expiration notifications at least 10 days in advance. While this duration can vary based on the client’s preferences, a 10-day lead time is generally recommended.	1.Ensure compliance with the licensed terms and conditions regarding user counts, concurrent connections, or processing capacity. 2.Adjust workflows or configurations within Adeptia to optimize resource usage and stay within licensed limits. Implement proactive monitoring of license usage and adjust thresholds or configurations accordingly to prevent future breaches.
abpm.diagnostics.kernel.heap.threshold	1.Heap Memory Exceedance: The threshold indicates that the JVM heap memory allocated for Adeptia ABPM has reached or exceeded a predefined limit. 2.Memory Leakage: Potential memory leaks within custom processes or configurations running on Adeptia ABPM. 3.Increased Workload: Sudden increase in processing load or data volume without corresponding adjustment in JVM heap settings.	Logs and Alerts: Review system logs for any heap memory-related warnings or errors.By default it is 80% .It is client dependent recommended to setup 80-85% Performance Analysis : Analyze system performance during peak loads or specific processing tasks to identify memory usage patterns.	Increase Heap Size: Adjust JVM heap size parameters (-Xmx and -Xms flags in JVM startup options) to allocate more memory if the current heap size is insufficient.
abpm.diagnostics.webrunner.heap.threshold	1.Heap Memory Exceedance: The threshold indicates that the JVM heap memory allocated for Adeptia WebRunner has reached or exceeded a predefined limit. 2.Memory Leakage: Potential memory leaks within WebRunner or custom applications deployed on it. 3.Increased Load: Sudden increase in concurrent user sessions or processing demands on Adeptia WebRunner.	eview system logs for any heap memory-related warnings or errors specifically related to WebRunner. Analyze system performance during peak usage periods to identify memory usage patterns By default it is 80% .It is client dependent recommended to setup 80-85%	Adjust JVM heap size parameters (-Xmx and -Xms flags in JVM startup options) to allocate more memory if the current heap size is insufficient for WebRunner. Ensure proper resource cleanup and effective garbage collection Consider scaling out WebRunner instances to distribute load and reduce individual JVM heap pressure. Implement monitoring of JVM heap usage for WebRunner and adjust thresholds or configurations as needed to prevent future issues.
abpm.diagnostics.queueprocessoer.threshold	Queue Backlog: The threshold indicates that the processing queue length or backlog has reached or exceeded a predefined limit. 2.Configuration Issues: Misconfiguration of queue processor settings or parameters	Review system logs for any alerts or warnings related to queue processor thresholds. Analyze system performance metrics during peak processing times to identify queue-related issues.	Review and adjust queue processor settings (such as thread pool size, max queue size) to optimize for current workload Consider scaling out queue processor instances to distribute processing load and reduce backlog. Implement load balancing strategies to evenly distribute incoming tasks across multiple queue processor instances. Optimize system resources (CPU, memory) to improve queue processing speed and reduce backlog.
abpm.diagnostics.cpu.usage.threshold	1.High CPU Utilization: The threshold indicates that CPU usage within Adeptia ABPM has reached or exceeded a predefined limit. 2.Increased Workload: Sudden spikes in processing tasks, concurrent user sessions, or data volume impacting CPU performance.	Review system logs for any CPU usage-related warnings or errors. Analyze system performance metrics during peak usage periods to identify CPU usage patterns and potential bottlenecks.	Review and optimize processes and integrations within ABPM to reduce CPU overhead.