Our next-gen architecture is built to help you make sense of your ever-growing data Watch a 4-min demo video!
Formats: PNG, PDF, and SVG
Files size: 2.8 MB
For brand guidelines, please click here
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:
1. Sign up for a Coralogix account. Set up your account on the Coralogix domain corresponding to the region within which you would like your data stored.
2. Access your Coralogix private key.
3. Configure a metrics bucket in your Coralogix dashboard. 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’.
STEP 3. Scroll down to ‘Destination settings’.
|Coralogix – US||https://firehose-ingress.coralogix.us/firehose|
|Coralogix – Singapore||https://firehose-ingress.coralogixsg.com/firehose|
|Coralogix – Ireland||https://firehose-ingress.coralogix.com/firehose|
|Coralogix – India||https://firehose-ingress.coralogix.in/firehose|
|Coralogix – Stockholm||https://firehose-ingress.eu2.coralogix.com/firehose|
STEP 4. Scroll down to ‘Parameters’:
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 wanted value.
The source of the data in firehose determines the ‘integrationType’ parameter value:
STEP 5. Scroll down to ‘Backup settings’:
STEP 6. Review your settings and choose ‘Create delivery stream’.
Metrics subscribed to your delivery stream will be immediately sent and available for analysis within Coralogix.
To start sending your metrics to coralogix you first need to create a metric stream.
Go to the Cloudwatch console and choose ‘Streams’ under the ‘Metrics’ side menu.
Click on ‘Create metric stream’
Under ‘Metrics to be streamed’:
Scroll down to ‘Configuration’:
Scroll down to ‘Change output format’
Scroll down to ‘Custom metric stream name’ and pick a name for the metrics stream.
Scroll down and click on ‘Create metric stream’.
After a few minutes, the metrics will start streaming to coralogix and you will see them on the Grafana dashboard.
Common destinations errors that firehose might show 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|
To get the most out of the platform, be sure to check out the documentation which will help you get started with everything from parsing and enrichment to alerting and data clustering.
If you have questions about the configuration or want help diving into more advanced features, our support team is available 24/7 via our in-app chat!