You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: aws/logs_monitoring/README.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,10 +35,13 @@ Note: you can find the installed Forwarder under the stack's "Resources" tab.
35
35
Since version 3.0.0, the forwarder Lambda function is managed by CloudFormation. To upgrade an older forwarder installation to 3.0.0 and above, follow the steps below.
36
36
37
37
1. Install a new forwarder following the [installation](#installation) steps.
38
-
1. Manually migrate a few triggers on the old forwarder to the new one.
39
-
1. Ensure the new forwarder is working as expected.
38
+
1. Manually migrate a few triggers (CloudWatch log group subscription filter and S3 bucket event notification) on the old forwarder to the new one.
39
+
1. Ensure the new forwarder is working as expected, i.e., being invoked regularly without errors.
40
+
1. Ensure the logs from the migrated triggers (sources) are showing up in Datadog log explorer and look right to you.
40
41
1. Update all the triggers on the old forwarder to the new one, following these [steps](https://docs.datadoghq.com/integrations/amazon_web_services/?tab=allpermissions#send-aws-service-logs-to-datadog).
42
+
1. Ensure the old forwarder Lambda function's invocations count drops to zero.
41
43
1. Delete the old forwarder Lambda function when you feel comfortable.
44
+
1. If you have old forwarder Lambda functions installed in multiple AWS accounts and regions, repeat the steps above in every account and region combination.
read -p "About to bump the version from ${CURRENT_VERSION} to ${VERSION}, create a release aws-dd-forwarder-${VERSION} on Github and upload the template.yaml to s3://${BUCKET}/aws/forwarder/${VERSION}.yaml. Continue (y/n)?" CONT
49
-
if [ "$CONT"!="y" ];then
50
-
echo"Exiting"
51
-
exit 1
52
-
fi
43
+
if [ "$PROD_RELEASE"=true ] ;then
53
44
54
-
# Bump version number
55
-
echo"Bumping the current version number to the desired"
git commit -m "Bump version from ${CURRENT_VERSION} to ${VERSION}"
62
-
git push origin master
56
+
# Confirm to proceed
57
+
read -p "About to bump the version from ${CURRENT_VERSION} to ${VERSION}, create a release aws-dd-forwarder-${VERSION} on Github and upload the template.yaml to s3://${BUCKET}/aws/forwarder/${VERSION}.yaml. Continue (y/n)?" CONT
58
+
if [ "$CONT"!="y" ];then
59
+
echo"Exiting"
60
+
exit 1
61
+
fi
63
62
64
-
# Create a github release
65
-
echo"Release aws-dd-forwarder-${VERSION} to github"
66
-
go get github.com/github/hub
67
-
rm -f aws-dd-forwarder-*.zip
68
-
zip -r aws-dd-forwarder-${VERSION}.zip .
69
-
hub release create -a aws-dd-forwarder-${VERSION}.zip -m "aws-dd-forwarder-${VERSION}" aws-dd-forwarder-${VERSION}
63
+
# Get the latest code
64
+
git pull origin master
65
+
66
+
# Bump version number
67
+
echo"Bumping the current version number to the desired"
echo"About to release non-public staging version of forwarder, upload aws-dd-forwarder-${VERSION} to s3, and upload the template.yaml to s3://${BUCKET}/aws/forwarder-staging/${VERSION}.yaml"
0 commit comments