chore: disable honeycomb export, remove vars

.circleci/config.yml

@@ -331,9 +331,6 @@ jobs:
       mongodb-password:
         description: "Shuttle shared mongodb password"
         type: env_var_name
-      honeycomb-api-key:
-        description: "Shuttle honeycomb api key for observability based on environment"
-        type: env_var_name
       deploys-api-key:
         description: "Shuttle api key used by the gateway to authorise starting idle deployments"
         type: env_var_name
@@ -382,7 +379,6 @@ jobs:
             MONGO_INITDB_ROOT_PASSWORD=${<< parameters.mongodb-password >>} \
             DD_API_KEY=$DD_API_KEY \
             DD_ENV=<< parameters.shuttle-env >> \
-            HONEYCOMB_API_KEY=${<< parameters.honeycomb-api-key >>} \
             DEPLOYS_API_KEY=${<< parameters.deploys-api-key >>} \
             LOGGER_POSTGRES_URI=${<< parameters.logger-postgres-uri >>} \
             STRIPE_SECRET_KEY=${<< parameters.stripe-secret-key >>} \
@@ -658,7 +654,6 @@ workflows:
           name: Deploy images to unstable
           postgres-password: DEV_POSTGRES_PASSWORD
           mongodb-password: DEV_MONGO_INITDB_ROOT_PASSWORD
-          honeycomb-api-key: DEV_HONEYCOMB_API_KEY
           deploys-api-key: DEV_DEPLOYS_API_KEY
           logger-postgres-uri: DEV_LOGGER_POSTGRES_URI
           stripe-secret-key: DEV_STRIPE_SECRET_KEY
@@ -729,7 +724,6 @@ workflows:
           name: deploy-images-to-production
           postgres-password: PROD_POSTGRES_PASSWORD
           mongodb-password: PROD_MONGO_INITDB_ROOT_PASSWORD
-          honeycomb-api-key: PROD_HONEYCOMB_API_KEY
           deploys-api-key: PROD_DEPLOYS_API_KEY
           logger-postgres-uri: PROD_LOGGER_POSTGRES_URI
           stripe-secret-key: PROD_STRIPE_SECRET_KEY

DEVELOPING.md

@@ -87,8 +87,6 @@ make up
 
 > Note: `make up` can also be run with `SHUTTLE_DETACH=disable`, which means docker-compose will not be run with `--detach`. This is often desirable for local testing.
 >
-> Note: `make up` can also be run with `HONEYCOMB_API_KEY=<api_key>` if you have a honeycomb.io account and want to test the instrumentation of the services. This is mostly used only by the internal team.
->
 > Note: Other useful commands can be found within the [Makefile](./Makefile).
 
 The API is now accessible on `localhost:8000` (for app proxies) and `localhost:8001` (for the control plane). When running `cargo run -p cargo-shuttle` (in a debug build), the CLI will point itself to `localhost` for its API calls.

docker-compose.yml

@@ -272,7 +272,6 @@ services:
       - SHUTTLE_ENV=${SHUTTLE_ENV}
       - DD_API_KEY=${DD_API_KEY}
       - DD_ENV=${DD_ENV}
-      - HONEYCOMB_API_KEY=${HONEYCOMB_API_KEY}
     deploy:
       placement:
         constraints:

extras/otel/otel-collector-config.yaml

@@ -66,10 +66,6 @@ exporters:
       span_name_as_resource_name: true
       trace_buffer: 25
       # peer_tags_aggregation: true
-  otlp:
-    endpoint: "api.honeycomb.io:443"
-    headers:
-      "x-honeycomb-team": ${env:HONEYCOMB_API_KEY}
 service:
   pipelines:
     traces:

logger/src/dal.rs

@@ -110,8 +110,6 @@ impl Postgres {
                             if rx.len() >= 200 {
                                 warn!(
                                     queue_size = rx.len(),
-                                    // This string is matched in a honeycomb trigger, changing it will
-                                    // break the trigger.
                                     "database receiver queue is filling up"
                                 );
                             } else if !rx.is_empty() {