Events From different AWS Services
- Refer Here for the documentation
CloudWatch Logs
- Log can be defined as documentation of the event.
- To be able to monitor and draw insights from data, we need to collect the insights, aggregate and make it meaningful
- Life cycle of a log:
- Collection/Extraction:
- Logs need to be collected from source to the central location which will be responsible for storing the data.
- The Collection of logs is done using a log Agent which is a daemon process that helps to extract logs from a specific location.
- Amazon CloudWatch has an agent which can be installed on multiple OS (Linux or Windows) and it can send them over to CloudWatch for Storage
- Storage:
- Once the logs are collected, they need to be stored in particular location (database, filesystem, storage service)
- The data that is collected is going to be large, so storage needs to be realiable, scalable and highly available.
- CloudWatch logs is a solution that meedts all the requirements for storing data & more.
- When you use CloudWatch to store your infra & application logs, you do not have to worry anout the capacity of storage & availability of storage service.
- Cloud Watch logs also have sum extra features such as log retention policy.
- CloudWatch logs have a feature of archiving logs to S3 or Glacier.
- Analytics:
- Analyzing logs is all about to make sense of the data which we have collected.
- Cloud Watch Logs have the query feature
- Cloud Watch helps in doing aggregations on the log data collected
- Collection/Extraction:
