-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[IT-3975] Deploy opentelemetry collector (#14)
**Problem:** 1. An Opentelemetry collector needs to be deployed to ECS to support forwarding telemetry data for long-term storage and analysis. 2. A configuration file for the collector needs to be sourced from AWS secrets manager and injected into the Otel collector to configure the service. 3. Environment variables need to be updated in the schematic container to support configuring it to send telemetry data to the Otel collector. 4. A container level health check is needed as this service is not fronted by a load balancer. **Solution:** 1. Deploying the otel collector contributor container to ECS. I had attempted to use the AWS otel collector, however, they do not support the Oauth2 extension that we will use to attached an Auth header on out-going requests: aws-observability/aws-otel-collector#1492 2. Storing the otel config file in AWS Secret manager and injecting it into the Otel collector by overriding the docker CMD command on the container. 3. Setting environment variables on the schematic container to configure it sending telemetry data to the otel collector. 4. Pointing to our sage specific docker image that contains a binary compiled from golang that does container level health checks. **Testing:** 1. I verified that I was able to deploy both schematic and the otel collector to AWS ECS. 2. I verified that by setting the environment variables in schematic that it was able to produce, and forward it's data to the otel collector. 3. I verified that the otel collector was able to perform the oauth2 client credential exchange with Auth0 to obtain an access token. 4. I verified that both logs AND traces were forwarded to the kubernetes cluster/SigNoz and ingested into Clickhouse for long-term storage. 5. I verified that the telemetry data showed up in the SigNoz UI as expected.
- Loading branch information
1 parent
650c456
commit 6cbd1b6
Showing
4 changed files
with
244 additions
and
36 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters