This article explains how to inject an error reporting module using ChatOps and how it helps organizations react faster to issues arising from applications that were running inside AWS Lambda Functions. In this demo, I will be using NodeJS and will utilize Slack to deliver alarms to important stakeholders:

• Application Developers
• Software Managers
• Software Testers
• Security Response Team
• Whoever needs to be awake when something is broken

Benefits

Before we start coding, I think that it is necessary to understand the good things that ChatOps bring to the table so that we can explain to our software development teams the importance of the effort we are putting in building this alarm mechanism.

Early Detection of Software Issues

Hey, catching bugs in the development environment is the best thing a developer could be aiming for when making mistakes in the code. This allows you to peacefully google the application error and find the right way to fix it.

Rapid Response to Production Issues

Raising alarms to messaging-apps help software engineering teams to gain real-time visibility of issues that reached the production stage. This benefits the organization by reducing the downtime and impact of application issues on the business.

It Saves You from Silent Failures

Without ChatOps, background workers fail silently without having the decency to inform you that something went wrong in production. I find these background workers the nastiest of all as they can easily place your job security to a rocking chair. Installing proper error handling and alarm mechanisms save you from delivering broken work to production

Stimulates Collaboration and Learning

Raising issues in a channel where an entire team actively listens to benefit organizations subtly by raising awareness which trains your development team on the following topics:

• Why did an issue got raised
• Where the issue can be fixed
• How to fix the issue
• How to prevent it from happening again

#aws #nodejs #aws-lambda #slack #serverless