O&M phase
Updated at:
After developers deploy the code based on the requirements, they must handle exceptions related to data, programs, scheduling, and monitoring and alerting at the earliest opportunity to ensure the timeliness of data output, efficient execution of programs, and production stability.
Background information
Data developers must perform the following O&M operations:
- Handle program exceptions and optimize performance.
- Handle scheduling exceptions.
- Analyze exceptions related to data quality monitoring rules and optimize monitoring rules.
- Check data exceptions.
The O&M phase includes impact analysis, solution formulation and implementation, and solution verification.
Procedure
- Analyze the impact.
O&M personnel or developers identify exceptions related to metrics such as data output timeliness and data accuracy based on monitoring rules or by using self-discovery or other methods and then analyze the impact of the exceptions. Exceptions include but are not limited to:
- A task failed to run.
- A task is running for an extended period of time.
- Dirty data is found in the output table.
Developers determine whether online data applications are affected based on the impact analysis result.- If the impact is significant, developers must send an alert notification to the task owner at the earliest opportunity, determine the cause of the exception, and identify feasible solutions.
- If the impact is negligible, no subsequent process is required.
- Formulate and implement a solution.
- A developer submits an online change request.
- A reviewer approves the change deployment. The reviewer must be a user who is familiar with the business logic and code.
- O&M personnel perform the change deployment. After the deployment is complete, a data developer is notified for solution verification. If the verification fails, O&M personnel perform a rollback on the script and report the result to the developer.
- Verify the solution.
After O&M personnel notify the developer that the implementation is successful, the developer verifies whether the change meets expectations.
- If the change meets expectations, the developer informs the direct downstream and related parties of the reason, content, and effective time of the change.
- Otherwise, the developer provides feedback to O&M personnel to perform a rollback.
Is this page helpful?