The collector proxy uses a configuration key to authenticate to Honeycomb. This was the only api key type that existed when we set it up
However, honeycomb now supports Ingestion keys, which can only write data, not modify config.
We should switch the collector to using one of these keys instead.
Probably also should do the same for any other otel emitting services, e.g. job-server, opencodelists, controller, etc
The collector proxy uses a configuration key to authenticate to Honeycomb. This was the only api key type that existed when we set it up
However, honeycomb now supports Ingestion keys, which can only write data, not modify config.
We should switch the collector to using one of these keys instead.
Probably also should do the same for any other otel emitting services, e.g. job-server, opencodelists, controller, etc