-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Update to version v2.0.0 * fix: fix the gh-page workflow
- Loading branch information
Showing
807 changed files
with
66,934 additions
and
43,265 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,21 +1,78 @@ | ||
# Change Log | ||
|
||
All notable changes to this project will be documented in this file. | ||
|
||
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), | ||
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
||
## [1.0.3] - 2023-06-28 | ||
## [2.0.0] - 2023-08-22 | ||
|
||
### Added | ||
|
||
- Log ingestion from S3 bucket to support more log sources #89 | ||
- Show logs and metrics of the log analytics pipelines #112 | ||
- Quickly enable alarms on log ingestion pipeline #113 | ||
- Show the AWS resource changes when importing AOS using automatic networking mode #53 | ||
- Log Agent Installation: Support of agent installation on AL2023 instances #88 | ||
- Support of multi-AZ standby enabled OpenSearch cluster when creating log pipelines #170 | ||
- Instance Group: Show error message on the console when the installation of log agent fails #169 | ||
- Support same index name in different OpenSearch clusters #166 | ||
- Installation: refresh the aws-exports.json once update the CloudFormation input parameters #161 | ||
- Application log pipeline: Add a step to choose Log Config during the application pipeline creation steps #159 | ||
- Log Agent: Auto rotation of Fluent Bit log file #158 | ||
- Instance group: Add an option to attach IAM policies to Instance Group managed EC2 instances automatically #151 | ||
- Domain management: Check the prerequisites of OpenSearch clusters before import OpenSearch clusters #148 | ||
- Support ingest WAF (associate with CloudFront) sampled logs to OpenSearch in other regions except us-east-1 #129 | ||
|
||
### Fixed | ||
|
||
- Log Config: Time key in Fluent Bit config for Spring Boot should be time type instead of None #71 | ||
- EventBridge will be disabled automatically if deleting instances in instance group #164 | ||
- Log Config should not be created without Regex/Log Format #163 | ||
- Lack of region check before creating WAF log pipeline #162 | ||
- The Fluent bit configuration file generated in sidecar deployment option has a wrong shared volume #160 | ||
- S3 access log dashboard: 5xx Code description is covered #157 | ||
- S3 access log dashboard: The Average Time Unit should be milliseconds #155 | ||
- Cross-account: Unable to get instance list and create instance group in CN region #156 | ||
- The OpenSearch information (e.g., version, data nodes) is not updated automatically after customer upgraded the cluster #150 | ||
- Cannot differentiate the Lambda for different AWS Service log pipeline based on Lambda description #146 | ||
- Fix data lost when cannot find the location with IP address using MaxMind database #126 | ||
- Syslog: Fix port conflict when adding & deleting new log source in parallel #174 | ||
|
||
### Changed | ||
|
||
- Minimize the permissions of EC2 log ingestion IAM role #154 | ||
- Minimize the privileges of cross-account access role #153 | ||
- Soft delete when removing OpenSearch domain #152 | ||
- Save ALB access logs of Nginx based proxy to S3 bucket #149 | ||
- Code refactor: DynamoDB design optimization and GraphQL API design optimization #147 | ||
- Minimize security group egress of the provisioned ECS #145 | ||
- WAF dashboard: Cannot filter results using `nonTerminatingMatchingRules.action` field #144 | ||
|
||
### Removed | ||
|
||
- Domain management: Remove the support of Elasticsearch engine #176 | ||
|
||
## [1.0.3] - 2023-06-27 | ||
|
||
### Fixed | ||
- Fix the processor Lambda function urllib3 version issue | ||
|
||
- Fix the processor Lambda function urllib3 version issue #138 | ||
|
||
## [1.0.2] - 2023-06-21 | ||
|
||
### Fixed | ||
- Fix the EKS Fluent-Bit deployment configuration generation issue | ||
|
||
- Support generation of Kubernetes YAML configuration file for EKS 1.24~1.27 #133 | ||
|
||
## [1.0.1] - 2023-04-17 | ||
|
||
### Fixed | ||
|
||
- Fix deployment failure due to S3 ACL changes | ||
|
||
## [1.0.0] - 2023-03-16 | ||
|
||
### Added | ||
|
||
- All files, initial version |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
#!/bin/bash | ||
# | ||
# You can remove this script if you do NOT have unit test. | ||
# | ||
# This script should be run from the repo's deployment directory | ||
# cd deployment | ||
# ./run-unit-tests.sh | ||
# | ||
source_template_dir="$PWD" | ||
cd $source_template_dir/../source | ||
./run-all-tests.sh |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
../images |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
There are different types of log alarms: log processor alarms, buffer layer alarms, and source alarms (only for application log pipeline). The alarms will be triggered when the defined condition is met. | ||
|
||
| Log alarm type | Log alarm condition | Description | | ||
| -------------------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| Log processor alarms | Error invocation # >= 10 for 5 minutes, 1 consecutive time | When the number of log processor Lambda error calls is greater than or equal to 10 within 5 minutes (including 5 minutes), an email alarm will be triggered. | | ||
| Log processor alarms | Failed record # >= 1 for 1 minute, 1 consecutive time | When the number of failed records is greater than or equal to 1 within a 1-minute window, an alarm will be triggered. | | ||
| Log processor alarms | Average execution duration in last 5 minutes >= 60000 milliseconds | In the last 5 minutes, when the average execution time of log processor Lambda is greater than or equal to 60 seconds, an email alarm will be triggered. | | ||
| Buffer layer alarms | SQS Oldest Message Age >= 30 minutes | When the age of the oldest SQS message is greater than or equal to 30 minutes, it means that the message has not been consumed for at least 30 minutes, an email alarm will be triggered. | | ||
| Source alarms (only for application log pipeline) | Fluent Bit output_retried_record_total >= 100 for last 5 minutes | When the total number of retry records output by Fluent Bit in the past 5 minutes is greater than or equal to 100, an email alarm will be triggered. | | ||
|
||
You can choose to enable log alarms or disable them according to your needs. | ||
|
||
## Enable log alarms | ||
|
||
1. Sign in to the Centralized Logging with OpenSearch console. | ||
|
||
2. In the left navigation bar, under **Log Analytics Pipelines**, choose **AWS Service Log** or **Application Log**. | ||
|
||
3. Select the log pipeline created and choose **View details**. | ||
|
||
4. Select the **Alarm** tab. | ||
|
||
5. Switch on **Alarms** if needed and select an exiting SNS topic. | ||
|
||
6. If you choose **Create a new SNS topic**, you need to provide email address for the newly-created SNS topic to notify. | ||
|
||
## Disable log alarms | ||
|
||
1. Sign in to the Centralized Logging with OpenSearch console. | ||
|
||
2. In the left navigation bar, under **Log Analytics Pipelines**, choose **AWS Service Log** or **Application Log**. | ||
|
||
3. Select the log pipeline created and choose **View details**. | ||
|
||
4. Select the **Alarm** tab. | ||
|
||
5. Switch off **Alarms**. |
Oops, something went wrong.