With this integration, you can collect Logs from Carbon Black and forward them to Logz.io.
Set Carbon Black Event Forwarder
Follow Carbon Black instructions for forwarding events to S3 bucket
Create new stack
To deploy this project, click the button that matches the region you wish to deploy your Stack to:
Specify stack details
Specify the stack details as per the table below, check the checkboxes and select Create stack.
|The Logz.io listener URL for your region. (For more details, see the regions page||Required|
|Your Logz.io log shipping token.||Required|
|Log level for the Lambda function. Can be one of: ||Default: |
|The log type you'll use with this Lambda. This is shown in your logs under the type field in OpenSearch Dashboards. Logz.io applies parsing based on the log type.||Default: |
|Comma-seperated list of regexes that match the paths you'd like to pull logs from.||-|
|Fields from the path to your logs directory that you want to add to the logs. For example, ||-|
Give the stack a few minutes to be deployed.
Once your Lambda function is ready, you'll need to manually add a trigger. This is due to Cloudformation limitations.
Go to the function's page, and click on Add trigger.
Then, choose S3 as a trigger, and fill in:
- Bucket: Your bucket name.
- Event type: Choose option
All object create events.
- Prefix and Suffix should be left empty.
Confirm the checkbox, and click *Add.
That's it. Your function is configured. Once you upload new files to your bucket, it will trigger the function, and the logs will be sent to your Logz.io account.
S3 Hook will automatically parse logs in the following cases:
- The object's path contains the phrase
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open OpenSearch Dashboards.
If you still don't see your logs, see Log shipping troubleshooting.