Building Effective Business Monitoring and Alerting for Logistics Platforms

Background

In routine operations and incident response, system‑level metric anomalies often coincide with business‑level metric anomalies, but the reverse is not always true, leading to delayed detection of business issues and potential large‑scale impact on logistics stability and user experience.

Business Monitoring Solution

The generic data‑monitoring process includes data collection, aggregation, threshold configuration, and dashboard display. Internally, three DevOps platforms—UMP, PFinder, and Taishan—provide business‑monitoring applications for KA merchants.

UMP Business Monitoring

UMP was the earliest platform and is now offline, but its monitoring continues for some applications.

PFinder Business Monitoring

In the fast‑delivery order process, when package count exceeds a threshold, orders are moved to a separate group and throttled. PFinder tracks package counts, monitors per‑minute totals, and triggers alerts when thresholds are crossed.

Taishan Business Monitoring

Taishan is the most widely used platform for KA merchants. It standardizes log format, coding practice, data visualization, alert configuration, and best practices.

Unified Log Format

Business domain and sub‑domain

Business scenario (order type)

Channel source (JOS, EDI, gateway, WMS, etc.)

Merchant code and department code (key for monitoring by merchant or department)

Density (request count)

Result (Y/N)

Result code and description

Result sub‑code and description

Merchant order number

Order number and waybill number

|业务域|业务子域|业务场景|渠道来源|商家编码|密度|结果(Y/N)|结果码|结果码描述|结果子码|结果子码描述|商家单号|订单号|运单号

Coding Practices

Log4j Configuration

<property name="patternLayout">%d{yyyy-MM-dd HH:mm:ss.SSS}-%X{PFTID}-%-5p - [%t] %c -%m%n</property>
<RollingRandomAccessFile name="businessFile" fileName="${log_path}/eclp-biz-eclp-isv-business.log" filePattern="${log_path}/eclp-biz-eclp-isv-business-%i.log">
    <PatternLayout charset="UTF-8" pattern="${patternLayout}"/>
    <Policies>
        <SizeBasedTriggeringPolicy size="1GB"/>
    </Policies>
    <DefaultRolloverStrategy max="5"/>
</RollingRandomAccessFile>
<AsyncLogger name="BusinessLogger" level="INFO" additivity="false" includeLocation="false">
    <AppenderRef ref="businessFile"/>
</AsyncLogger>

Business Log Printing

/**
 * Business log
 */
private static final Logger blogger = LoggerFactory.getLogger("BusinessLogger");
blogger.info("|订单域|销售出|下单|{}|{}|{}|{}|{}|{}|{}|{}|{}|{}|{}|{}", order.getSourceChannel(), order.getShopNo(), order.getDepartmentNo(), 1, result, code, message, subCode, subMessage, order.getIsvUUID(), context.getPin(), soNo);

Data Visualization

Taishan dashboards display minute‑level metrics per department, using tables for order counts and graphs for success rates and failure counts.

Alert Rules

Success Rate Alert

Trigger when success rate falls below 50% for two consecutive intervals.

Volume Spike/Drop Alerts

Configure thresholds based on minute‑level volume comparisons with yesterday and last week to reduce false alarms.

Best Practices

Merchant warehouse migration caused low success rates; after migration, rates recovered.

Repeated order submissions generated duplicate‑submission errors; adjusting retry logic resolved the issue.

Insufficient inventory led to failures; adding retry after stock replenishment improved success.

Department switches caused temporary alert spikes; coordinating switches reduced noise.

Product level adjustments impacted inventory availability, triggering alerts.

External GIS API timeouts required monitoring of third‑party dependencies.

OAID verification failures were traced to outdated recipient information.

Incorrect pickup time validation caused order rejections.

Parameter errors required merchant system checks.

Upstream traffic anomalies produced sudden volume drops; coordination with upstream teams resolved them.

Conclusion

Through continuous improvement of monitoring capabilities and alert rules, the team now detects and resolves merchant issues promptly, enhancing system availability and merchant experience.