This guide shows you how to create a Docker image that is based on v0.62.0 release of OpenTelemetry Collector and send your data to Coralogix. By creating a specific image that forwards your metrics and traces to Coralogix, Coralogix allows you to run your application on ECS together with our container image.
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. Create an active AWS account with the relevant permissions.
1. Log into the AWS Portal and search for the Amazon Elastic Container Service page.
2. Select Create cluster.
3. Select EC2 Linux + Networking. Click Next step.
4. Configure the cluster.
5. When complete, click View Cluster.
To begin sending telemetry data from your ECS – EC2 instance to Coralogix, you will need to create a new Task Definition.
1. In your ECS console, select Task Definitions > Create new Task Definition.
2. Select launch type compatibility: EC2 > Next step.
3. Configure task and container definitions.
{ "ipcMode": null, "executionRoleArn": null, "containerDefinitions": [ { "dnsSearchDomains": null, "environmentFiles": [], "logConfiguration": null, "entryPoint": [], "portMappings": [ { "hostPort": 0, "protocol": "tcp", "containerPort": 4317 } ], "command": [], "linuxParameters": null, "cpu": 0, "environment": [ { "name": "OTEL_RESOURCE_ATTRIBUTES", "value": "APP_NAME=Otel,SUB_SYS=OTEL" }, { "name": "PRIVATE_KEY", "value": "" }, { "name": "TRACES_ENDPOINT", "value": "otel-traces.<domain>:443" }, { "name": "METRICS_ENDPOINT", "value": "otel-metrics.<domain>:443" } ], "resourceRequirements": null, "ulimits": null, "dnsServers": null, "mountPoints": [ { "sourceVolume": "hostfs", "containerPath": "/hostfs", "readOnly": "" } ], "workingDirectory": null, "secrets": null, "dockerSecurityOptions": null, "volumesFrom": null, "stopTimeout": null, "image": "coralogixrepo/otel-coralogix-ecs", "startTimeout": null, "firelensConfiguration": null, "dependsOn": null, "disableNetworking": null, "interactive": null, "healthCheck": null, "essential": true, "links": null, "hostname": null, "extraHosts": null, "pseudoTerminal": null, "user": null, "readonlyRootFilesystem": null, "dockerLabels": null, "systemControls": null, "privileged": null, "name": "otel", "repositoryCredentials": { "credentialsParameter": "" } } ], "taskRoleArn": "", "family": "Otel", "pidMode": null, "requiresCompatibilities": [ "EC2" ], "networkMode": "bridge", "runtimePlatform": null, "inferenceAccelerators": [], "proxyConfiguration": null, "volumes": [ { "host": { "sourcePath": "/" }, "name": "hostfs" } ], "placementConstraints": [], "tags": [] }
TRACES_ENDPOINT
: In order to send traces to Coralogix, you will need to include your account’s specific domain in the Coralogix endpoint: otel-traces.<domain>:443
.METRICS_ENDPOINT
: In order to send metrics to Coralogix, you will need to include your account’s specific domain in the Coralogix endpoint: otel-metrics.<domain>:443
.PRIVATE_KEY
: Access your Coralogix private key. Ensure that this sensitive information remains protected and unexposed.OTEL_RESOURCE_ATTRIBUTES
: Defines your application
& subsystem
names. If unchanged, this sets your application name to “Otel” and subsystem name to “OTEL.”1. In your cluster, click Create under the Service tab.
2. Under ‘Configure service’:
3. Under ‘Configure network’:
4. Review and click Create Service.
5. Click View Service.
Github | Official OpenTelemetry Collector with Coralogix Exporter |
Features | Coralogix APM features APM using Amazon EC2 |
Need help?
Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.
Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].