When a client interrupted Hany’s lunch in late 2017 with an urgent request, he immediately jumped into their system to find an answer. This client had an agreement to provide sensitive data on a nightly basis to a partner. This was automated, the process called a cron job.
The problem: One night the data was never received by the partner.
Hany shifted into troubleshooting mode, working with his client to examine the guts of their system. It appeared the job did run as scheduled, even though the partner did not receive the file.
Hany investigated the missing file of sensitive data, while his client and their partner pointed fingers at each other over fault. All the while, he asked himself: “What happened?”
Digging deeper into alert files, database logs and network graphs didn’t shed any more light on the problem. After examining all the evidence and chasing down logical leads, Hany was no further ahead.
That night at home, he was distracted by the problem. After a late-night of research, he was no further ahead. Over a cup of strong coffee the next morning, he spotted an obscure forum post he had disregarded the night before. The post gave his investigation a new avenue to explore – Process Accounting.
With more sleuthing, hiking through the historical bowels of the internet, and combing through 1000 lines of code, Hany was rewarded with an answer and knew what the client’s problem was and who was at fault.
For the whole story, all the technical details, and Hany’s insider view, listen to the episode.
If you enjoyed this episode, please share it with anyone you think will enjoy it. And if you can give us a review on Apple Podcasts, we’ll be grateful!