fun-with-serverless / whatsapp-logger Goto Github PK

1. Add CW alerts in case DLQ has messages in it
2. Add distributed tracing for our Serverless stack.

Follow best practices as defined by

• https://aws.amazon.com/blogs/developer/recommended-aws-cdk-project-structure-for-python-applications/
• https://www.ranthebuilder.cloud/post/aws-cdk-best-practices-from-the-trenches

1. Avoid leaving old chats
2. Backup those chats for future references

The image used for the whatsapp listener is too big. Reduce its size.

Use the same interfaces to add multiple whatsapp agents

In case a user answers someone, mark that the message is answer so chatGPT can produce better summary results

Reduce the cost of the fargate instance

Lambdas can sometimes become too large to view in the Console editor, making it difficult to manage and edit the code online. One solution to this issue is to use Layers, which can help reduce the overall size of the Lambda and make it more manageable.

Use https://github.com/aws-hebrew-book/whatsapp-logger/blob/8a9afb0bab0d4c3c6590e5660120af41bb4eaba5/backend/src/utils/models.py#L10 in https://github.com/aws-hebrew-book/whatsapp-logger/blob/8a9afb0bab0d4c3c6590e5660120af41bb4eaba5/backend/src/googlesheets_recorder/app.py#L24

1. Define which groups require a summary
2. Do you want to send the summary to the group itself or you personal channel

(node:1) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy

Right now you are either sending to the original group or to yourself, allow sending to other groups as well.

Use OpenAI here

We are currently using 3.9

Add github flow

A few days ago Whatsapp changed and no longer shows logs on the web like before. You will only see records of chats that took place between now and 24 hours ago or you will only have the last message. Any workaround for this?

Add statistics like:

• Last message arrived at ...
• Total messages arrived today
• Total messages arrived this week
• Total messages arrived this month

And have the ability to view them in the dashboard

Currently the whatsapp listener module does not have any unit tests. Write some.

Using NAT Getway is the right solution in production, bit it's extremly expensive in dev environments. Move to NAT instance when deploying to non prod environments.

See https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.NatProvider.html

Tracking issue for:

• https://github.com/aws-hebrew-book/whatsapp-logger/security/code-scanning/1