Amazon Kinesis Data Firehose delivers real-time streaming data to destinations like Amazon Simple Storage Service (Amazon S3), Amazon Redshift, or Amazon OpenSearch Service (successor to Amazon Elasticsearch Service), and now supports delivering streaming data to Coralogix. There is no limit on the number of delivery streams, so it can be used for getting data from multiple AWS services.
Coralogix is an AWS Partner Network (APN) Advanced Technology Partner with AWS Competencies in DevOps. The platform enables you to easily explore and analyze logs, metrics, and traces to gain deeper insights into the state of your applications and AWS infrastructure. You can analyze all your AWS service metrics to uncover trends in your AWS services.
Using Coralogix with Amazon Kinesis Data Firehose offers a few significant benefits compared with other solutions:
It keeps monitoring simple.
It integrates flawlessly.
It’s flexible with minimum maintenance.
Scale, scale, scale.
Metrics bucket configured in your Coralogix dashboard [In your Coralogix toolbar, navigate to Data Flow > Setup Archive.]
STEP 1. Go to the Kinesis Data Firehose console and choose ‘Create delivery stream’.
STEP 2. Under ‘Choose source and destination’.
Source: Direct PUT
Delivery stream name: Fill in the desired stream name.
By default, your delivery stream arn and name will be used as ‘applicationName’ and ‘subsystemName’. To override the associated ‘applicationName’ or ‘subsystemName’, add a new parameter with the desired value.
Key: ‘applicationName’ , value – ‘new-app-name’
Key: ‘subsystemName’ , value – ‘new-subsystem-name’
The source of the data in firehose determines the ‘integrationType’ parameter value:
STEP 5. Optionally, add environment variables to configure the Lambda, as described in the configuration.
STEP 6. The Lambda function is ready to be used in Kinesis Data Firehose Data Transformation. Please note the function ARN and provide it in the relevant section of the Kinesis Data Firehose configuration.
In order to prevent a delay in the delivery of your data, and depending on the size of your setup, we recommend adjusting your Lambda buffer hint and Kinesis Data Firehose buffer size configuration accordingly. For optimal experience, we recommend setting the Lambda buffer hint to 0.2 MB and the Kinesis Data Firehose buffer size to 1 MB. Note that this may cause more frequent Lambda runs, which may result in higher costs.
You can check the staleness of your data in your Kinesis Data Firehose delivery stream in the Monitoring tab by looking at the ‘Delivery to HTTP endpoint data freshness’. If you see the staleness value grow, this may indicate the Lambda function runs are too slow. In such a case, you may increase the Lambda’s memory and set the buffering configuration as described above.
View these common destinations errors and their possible solutions.
The delivery timed out before a response was received and will be retried. If this error persists, contact the AWS Firehose service team.
None needed – no data loss
Delivery to the endpoint was unsuccessful. See Troubleshooting HTTP Endpoints in the Firehose documentation for more information. Response received with status code 502.
Coralogix returned HTTP 502 error code, firehose will resend the data. None needed – no data loss