Source and classification

• Source: ZNS Network Service 1.2.0 known issue record.
• Classification: Product issue.
• Confirmation basis: This behavior has been confirmed as a known issue in ZNS Network Service 1.2.0.

Issue metadata

• Issue ID: ZCF-4972.
• Component/product: Observability analysis and log query.
• Status: Open.
• Priority/severity: P2.
• Affected version: 1.2.0.

Problem description

When an application reports an error, a sequence of error details and call information that should be displayed together may be split into multiple records in the log list. Opening a single log record does not show the complete context.

Symptoms

• One complete error message is split into multiple lines or log records.
• The details of a single record do not contain the complete error cause or call process.
• Adjacent logs must be combined to reconstruct the same operation.

Impact

The complete error cannot be understood from a single record, and contextual information for the same error may be missed.

Workaround

1. Record the approximate time when the error occurred and sort the logs chronologically.
2. Review adjacent logs from several seconds before and after the error and read the continuous content together.
3. Use trace_id or request_id to search for records related to the same operation.
4. If the page content is still incomplete, view the original log file on the corresponding ZNS node.

Affected products

• Product: ZCF.
• Component: Network Service.
• Version: 1.2.0.

Fix status

• Current status: Pending fix.
• Related patch/fix package: No separate patch information is available.

Related information

• Related Jira: ZCF-4972.