You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Refinery 2.8.4 (and main), Refinery's file_config.go doesn't appear to reference the CmdEnv loading of the REFINERY_API_HOST for configuring sending Refinery telemetry to Honeycomb.
But in the telemetry sections like [OTelMetricsConfig[(https://github.com/honeycombio/refinery/blob/fa1520ca28519393f9262126e96ad1a38d35b3dc/config/file_config.go#L270), that cmdenv isn't referenced for the APIHost Option:
Try to use the REFINERY_API_HOST environment variable to send metrics or logs of Refinery operations to Honeycomb.
Additional context
Not sure if this should use the same environment variable or not (probably should), but want to give the option of creating a REFINERY_TELEMETRY_API_HOST so that folks can send their Refinery telemetry to a different endpoint than they're sending their application telemetry.
The text was updated successfully, but these errors were encountered:
In Refinery 2.8.4 (and main), Refinery's file_config.go doesn't appear to reference the CmdEnv loading of the REFINERY_API_HOST for configuring sending Refinery telemetry to Honeycomb.
It looks like it loads correctly in the network config:
See the
cmdenv:"HoneycombAPI"
But in the telemetry sections like [OTelMetricsConfig[(https://github.com/honeycombio/refinery/blob/fa1520ca28519393f9262126e96ad1a38d35b3dc/config/file_config.go#L270), that
cmdenv
isn't referenced for the APIHost Option:Versions
Steps to reproduce
REFINERY_API_HOST
environment variable to send metrics or logs of Refinery operations to Honeycomb.Additional context
Not sure if this should use the same environment variable or not (probably should), but want to give the option of creating a REFINERY_TELEMETRY_API_HOST so that folks can send their Refinery telemetry to a different endpoint than they're sending their application telemetry.
The text was updated successfully, but these errors were encountered: