Message VPN

Message VPN replication status is down.

Predicted Impact: If the replication status remains down, messages and configuration may not be correctly replicated to the configured Disaster Recovery (DR) site.

Recommended Actions: Verify the event broker's replication configuration. For mitigation recommendations, consult the related syslog event documentation. For more information, Contact Solace.

Message VPN replication status has been down for a sustained period.

Predicted Impact: If the replication status remains down, messages and configuration may not be correctly replicated to the configured Disaster Recovery (DR) site.

Recommended Actions: Verify the event broker's replication configuration. For mitigation recommendations, consult the related syslog event documentation. For more information, Contact Solace.

Messages configured for synchronous replication can no longer be delivered to the standby site as fast as they are being received by the active site.

Predicted Impact: Messages requiring synchronous replication are downgraded to asynchronous replication, creating potential consistency issues between sites.

Recommended Actions: Verify the stability of the connection to the standby site and ensure there is sufficient bandwidth. For mitigation recommendations, consult the related syslog event documentation. For more information, Contact Solace.

Messages configured for asynchronous replication are affected by downgrade conditions, where messages can no longer be delivered to the standby site as fast as they are being received by the active site.

Predicted Impact: Messages requiring asynchronous replication experience further degradation, potentially impacting disaster recovery capabilities.

Recommended Actions: Verify the stability of the connection to the standby site and ensure there is sufficient bandwidth. For mitigation recommendations, consult the related syslog event documentation. For more information, Contact Solace.

Messages can no longer be delivered to the standby site as fast as they are being received by the active site.

Predicted Impact: All messages that require synchronous replication are downgraded to asynchronous replication.

Recommended Actions: Verify the stability of the connection to the standby site and ensure there is sufficient bandwidth. For mitigation recommendations, see the SYSTEM_CFGSYNC_ logs in the Syslog Events Reference or Contact Solace for more information.

For a sustained period, messages can no longer be delivered to the standby site as fast as they are being received by the active site.

Predicted Impact: All messages that require synchronous replication are downgraded to asynchronous replication.

Recommended Actions: Verify the replication configuration for the event broker. For mitigation recommendations, see the VPN_REPLICATION_* logs in the Syslog Events Reference. For more information, contact Solace.

Message VPN AMQP connection utilization threshold breach. AMQP connection utilization exceeds the monitor thresholds.

Predicted Impact: If the number of AMQP connections reaches the maximum number of connections (100% of capacity), new AMQP connections will be rejected.

Recommended Actions: Scale up the class of the messaging service to allow more connections. Otherwise, if possible, contact the support or development team of the client applications connected to the event broker to verify if the number of connections being used by those applications is reasonable.

Message VPN MQTT connection utilization threshold breach. MQTT connection utilization exceeds the monitor thresholds.

Predicted Impact: If the number of MQTT connections reaches the maximum number of connections (100% of capacity), new MQTT connections are rejected.

Recommended Actions: Scale up the class of the event broker to allow more connections. Otherwise, if possible, contact the support or development team of the client applications connected to the event broker to verify if the number of connections being used by those applications is reasonable.

Message VPN REST incoming connection utilization threshold breach. Incoming REST connection utilization exceeds the monitor thresholds.

Predicted Impact: If the number of incoming REST connections reaches the maximum number of connections (100% of capacity), new incoming REST connections will be rejected.

Recommended Actions: Upscale the class of the event broker to allow more connections.

Message VPN REST outgoing connection utilization threshold breach. Outgoing REST connection utilization exceeds the monitor thresholds.

Predicted Impact: If the number of outgoing REST connections reaches the maximum number of connections (100% of capacity), new outgoing REST connections can no longer be initiated by the event broker.

Recommended Actions: Upscale the class of the event broker to allow more connections.

Message VPN SMF connection utilization threshold breach. SMF connection utilization exceeds the monitor thresholds. If the number of SMF connections reaches maximum available, new SMF connections may be rejected.

Predicted Impact: If the number of SMF connections reaches the maximum number of connections (100% of capacity), new SMF connections are rejected.

Recommended Actions: Upscale the class of the messaging service to allow more connections. Otherwise, if possible, contact the support or development team of the client applications connected to the event broker to verify if the number of connections being used by those applications is reasonable.

Message VPN total connection utilization threshold breach. Total connection utilization exceeds the monitor thresholds. If the number of connections reaches total max connections, new connections of any kind may be rejected.

Predicted Impact: If the number of connections reaches the maximum number of connections (100% of capacity), new connections of any kind are rejected.

Recommended Actions: Upscale the class of the event broker to allow more connections.
If possible, contact the support or development team for the client applications that are connected to the event broker to verify that the number of connections being used by the client applications is reasonable.

Message VPN Web connection utilization threshold breach. Web connection utilization exceeds the monitor thresholds. If the number of Web connections reaches maximum available, new Web connections may be rejected.

Predicted Impact: If the number of Web connections reaches the maximum number of connections (100% of capacity), new Web connections will be rejected.

Recommended Actions: Upscale the event broker to allow more connections. Otherwise, if possible, contact the support or development team of the client applications connected to the event broker to verify if the number of connections being used by those applications is reasonable.

Message spool egress flow utilization threshold breach.

Predicted Impact: If the egress flow is utilized to 100% of capacity (resources are exhausted) for a queue or topic endpoint, consumers will not be able to bind or initiate a flow of messages from the persistent endpoint.

Recommended Actions: Remove any unused egress flows from the Message VPN, disconnect consumer applications using Guaranteed Messaging that are not needed, or upscale the event broker. Otherwise reduce the egress flow use to ease demand.

Message Spool Endpoint utilization breach. Endpoint utilization within a Message VPN exceeded the monitor thresholds. It will not be possible to create queues or topics.

Predicted Impact: If the endpoint utilization within the Message VPN's message spool endpoint is utilized to 100% of capacity (resources are exhausted), queues or topic endpoints cannot be created.

Recommended Actions: Remove any unused endpoints from the Message VPN. Otherwise, reduce endpoint use to ease demand.

Message spool Ingress Flow utilization threshold breach.

Predicted Impact: If the ingress flow is utilized to 100% of capacity (resources are exhausted), any publishers may not be able to send new Guaranteed Messages.

Recommended Actions: Remove any unused ingress flows from the Message VPN, otherwise reduce ingress flow use to ease demand. Disconnect some publishers that are not needed.

This is actively monitored with the Event Broker Logs monitor, which triggers notifications based on the thresholds set in the event broker. The use of the Event Broker Logs monitor provides more flexibility for different thresholds and allows every message spool to be monitored based on individual thresholds.

This monitor is not active and is available for use as a template or example. You can choose to clone the monitor and make it active to monitor message spools as a metric-based monitor.

The message spool utilization threshold for the Message VPN has been reached.

Predicted Impact: If the Message Spool is utilized to 100% of capacity (resources are exhausted), all Guaranteed (persistent) Messages are rejected on the affected event broker.

Recommended Actions: Reduce spool usage as necessary to ease demand or scale up the class of the event broker. Increase the message consumption rate or reduce the message publishing rate for Guaranteed Messaging. Contact Solace for assistance if necessary.

Message Spool Transacted Session utilization breach. Transacted session utilization exceeds the monitor thresholds.

Predicted Impact: If the Message Spool transacted session is utilized to 100% of capacity (resources are exhausted), new transacted sessions (or transacted connections to the event broker) cannot be created until the current sessions (connections) are closed.

Recommended Actions: Contact the support or development team for the client applications that establish the transacted sessions. That team should be consulted to ensure transacted sessions are used efficiently. Alternatively, reduce the transacted sessions to ease demand. Update applications to more efficiently close transacted sessions or otherwise reduce transacted session use to ease demand. Alternatively consider upscaling of the event broker.

Message spool Transaction utilization threshold breach. The transaction utilization exceeds the monitor thresholds.

Predicted Impact: New transactions may not be possible to be initiated in a transacted session until current transactions are committed.

Recommended Actions: Update applications to more efficiently close transactions or otherwise reduce transaction use to ease demand. Alternatively, upscale the class of the event broker.

The message VPN for the event broker may be down, leading to a potential service outage. Solace support has been notified and is working to resolve the situation.

Predicted Impact: There is an elevated risk for a service outage.

Recommended Actions: Contact Solace.