Skip to content

Release 0.3.0
Compare
Choose a tag to compare
@ivallhon ivallhon released this 06 Feb 11:37
· 266 commits to main since this release
v0.3.0
defeb27
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This new release adds several enhancements and changes to the dynatrace-aws-s3-log-forwarder:

  • Decoupling of the configuration of the log forwarder from code using AWS AppConfig. (Log forwarding and log processing rules format has changed, if you're upgrading read the notes below).
  • Make cross-account deployments easier to manage, EventBridge policies are now managed via SAM template.
  • Harmonize log attributes names with Dynatrace semantic attribute dictionary
  • Optimizations to Dockerfile
  • NotificationEmail parameter is now optional
  • Default to x86_64 architecture container images. Users can still chose to build arm64 images.
  • Documentation enhancements

Important notes for users upgrading:

  • The log forwarding Lambda function now defaults to load configuration from AWS AppConfig. You'll need to deploy the new SAM template.yaml version to create required resources. To keep loading configuration from local files set the parameter LogForwarderConfigurationLocation to local.
  • Log forwarding rules formatting has changed from a list of local files config/log_forwarding_rules/<bucket_name>.yaml format requiring a file per S3 bucket, to an array of log forwarding rules in YAML on an AWS AppConfig configuration profile named log-forwarding-rules (or optionally a local file config/log-forwarding-rules.yaml). You can find an example log-forwarding-rules configuration here. The previous format is still supported, but will be deprecated on upcoming releases.
  • Log processing rules formatting has changed from a list of local files config/log_forwarding_rules/<rule_name>.yaml format requiring a file per rule, to an array of log processing rules in YAML on an AWS AppConfig configuration profile named log-processing-rules (or optionally a local file config/log-forwarding-rules.yaml). You can find an example log-processing-rules configuration here.
  • Context attributes names added to logs have changed to be consistent with the sematric attributes dictionary:
    • log.source.bucket_name is now log.source.aws.s3.bucket.name
    • log.source.s3_key_name is now log.source.aws.s3.key.name
    • log.source.forwarder is now cloud.log_forwarder
  • Build instructions have changed and there's a previous step to download dependent AWS Lambda extensions.
Assets 2
Loading