My SMS alarm message is truncated. What needs to be done?
Solution: Go to the Admin tab -> Action / alarm Settings and click on the checkbox - 'Send Complete SMS Information, even if service provider restricts it' in that page.
By default , the complete information that you configure while adding SMS action is sent through the SMS. Some SMS service providers restrict the length of characters sent through the SMS. This could result in truncated message delivery. If you want to send only information on the Monitor, Attribute and its Severity, deselect this option. For E.g., "Health of JBoss Server is critical" will be the SMS message that is received in addition to the message provided when creating the SMS action.
New to ADSelfService Plus?
Related Articles
I am not getting the alarm even when the threshold limit is crossed. What needs to be done?
Solution: Check out the value in the Admin -> Action / Alarm Settings -> Consecutive Polls Count. That value determines how many poll intervals it should wait to determine whether alarm can be generated or not.Why don't I see the custom messages & replaceable tags given in an action in the alarm escalation notification ?
Alarm escalation provides the option for escalation if any alarm has not been attended for a given time period to an email address(s) or mobile number(s) or if a specific program was executed. The notification template & work flow logic used in the ...How to generate alarm history for more than 30 days
In Applications Manager, the alarm history for a monitor's attribute is preserved for a period of 30 days. This encompasses various metrics such as health, availability, and performance (individual attributes such as CPU Utilization, Memory ...Solaris Process arguments truncated after 80 characters.
In Solaris server, process arguments will be shown only 80 characters and remaining characters will be truncated. This is a limitation in AppManager.Critical\Warning alarm was raised, but action wasn't triggered
1.) Ensure that actions have been associated for the attribute that generated the alarm. For example, if the CPU utilisation of the server exceeded the permissible levels and generated the alarm, navigate to Monitor page-> Configure Alarm and ...