Issue

Use this article to troubleshoot SMS notification content truncation and template display issues.

Environment

• Product: ZCF
• Versions: 4.x, 5.x
• Component: Cloud
• Affected objects: SMS notification endpoints, alarm templates, management-node logs, and SMS provider channels
• Scenario: Customers receive platform alarms by SMS and rely on SMS content to locate resources.

Symptoms

• SMS alarms are sent successfully.
• Alarm resource names or fields in the SMS content are truncated with ellipses.
• The SMS provider reports that the platform-originated content already contains ellipses.
• Management-node logs also show incomplete resource names.

Possible causes

• The platform truncates the resource name when generating SMS content.
• SMS templates or backend field-length limits truncate the content.
• SMS provider or endpoint display limits cause the customer to see incomplete content.
• A resource name is too long and reaches a template display boundary.

Resolution

1. Collect the original SMS received by the customer, a screenshot of the platform alarm page, and the sending content in management-node logs.
2. Ask the SMS provider to confirm the actual received request content and determine whether truncation occurs on the platform or channel side.
3. Search management-node logs for the notification record and confirm whether the resource name sent by the platform already contains ellipses.
4. Record the resource-name length, alarm template, notification endpoint type, and Cloud version.
5. If the platform-side original content is already truncated, handle it as a template or product defect.

Key command

grep -a -nE "sms|SMS|Alarm|alarm|notification|notify" /usr/local/zstack/apache-tomcat/logs/management-server.log*

Remediation

• If the content received by the SMS provider already contains ellipses, track a platform template or product fix.
• If necessary, temporarily use email or HTTP notifications to obtain complete alarm content.
• When resource names are too long, optimize naming conventions if acceptable to the customer.

Verification

• Sending content in management-node logs contains the complete resource name.
• Request content received by the SMS provider matches platform logs.
• The customer can locate the alarm resource from the SMS, or details are completed through another notification method.

Risks and rollback

• A customer mobile-phone screenshot alone cannot determine the layer where truncation occurs.
• Before changing a template or notification method, confirm the customer alarm-receiving workflow.

Notes

• Before adjusting management services, databases, certificates, permissions, auditing, or security settings, confirm the HA state, service window, rollback plan, and compliance-retention requirements.
• If database modifications, underlying file operations, lock release, service restarts, driver or firmware upgrades, or bulk resource changes are required, contact ZStack technical support before proceeding.