One of the easiest ways to collect logs is to send all of them to S3 buckets.
We aim to help and make the log collection a breeze so we have An application published in AWS’s Serverless Application Repository.
I acknowledge that this app creates custom IAM roles and resource policies.
Once the deployment is done every new gzipped log file placed in the lambda will be sent to Coralogix
Variable | Description |
---|---|
Application Name | The stack name of this application created via AWS CloudFormation. If your log is JSON format, can use a Dynamic value from it. Example: $.level1.level2.value |
NotificationEmail | Failure notification email address |
S3BucketName | The name of the S3 bucket to watch |
ApplicationName | Application Name in Coralogix. |
BufferSize | Buffer size for logs in the lambda function. |
CoralogixRegion | The Coralogix location region [Europe, India, Singapore, US] Check your Coralogix account if url ends in .us its US. Region. Same for the others. |
Debug | Coralogix logger debug mode |
FunctionArchitecture | Our Function supports x86_64 or arm64 |
FunctionMemorySize | Max Memory for the function itself. |
FunctionTimeout | Function TimeOut |
NewlinePattern | Pattern for multiLine example: [\s(?={)|(?<=})\s,\s(?={)|(?<=})\s] |
PrivateKey | Your Coralogix account ‘send your logs’ key. Can be found in DataFlow -> API Keys |
SamplingRate | Sets the sampling rate |
SubsystemName | SubSystem name in Coralogix. If your log is JSON format, can use a Dynamic value from it. Example: $.level1.level2.value |
S3KeyPrefix | The S3 path prefix to watch, if you want to watch a particular subfolder within the bucket. |
S3KeySuffix | The S3 path suffix to watch |
We realize your infrastructure is rapidly growing.
You may wish to replicate this lambda or simply have multiple deployments managed as code.
We provide a terraform example just for that. You can find the Terraform module on GitHub