Context
Banking services run around the clock. When something fails in production, the incident record comes with an SLA, and the fix still has to go through the same release process as any other change.
Incident record
→Log4j2 log analysis on OpenShift
→Fix or hotfix
→CI/CD in Azure DevOps
→Digital.ai Release
→Production
My role
I provided production support for the services I worked on, from the first investigation to the fix reaching production.
What I did
- Traced production issues by analysing the Log4j2 logs of services running on OpenShift.
- Delivered bug fixes and hotfixes, resolving incident records within SLA.
- Supported releases and hotfixes up to production through CI/CD pipelines in Azure DevOps and Digital.ai Release.
- Troubleshot failed deployments and coordinated with the release team to get them through.
Outcome
Incident records were resolved within SLA, and fixes reached production through the standard release pipeline.
Details are generalised to respect client confidentiality. No customer data is shown.