Files
zeekay 10e6fec4c0 debrand: the brand token is INSIGHTS_, and a wrong one stops the container
The rule table mapped HOG_ -> FN_ ahead of any POSTHOG rule, so POSTHOG_FOO
split into POST + HOG_ and came out POSTFN_FOO. Nothing sets that. The live
pods set INSIGHTS_SKIP_MIGRATION_CHECKS, which bin/migrate-check reads on the
container entrypoint, so the misspelling does not degrade a feature -- it runs
migrate --check against a database whose history this tree does not share and
the container never starts.

Both replacements are measured against the shipped tree rather than chosen:
every HOG_ name with a counterpart there is spelled INSIGHTS_ (HOG_QL ->
INSIGHTS_QL, HOG_FUNCTION_TEMPLATES -> INSIGHTS_FUNCTION_TEMPLATES, 12 of 12
determinate cases), and FN_ appears in it nowhere. Upstream carries 95 HOG_
tokens and zero FN_ ones, so repairing FN_ back out is exactly the inverse of
the bad rule and cannot collide with an upstream name.

The rule is fixed for the next convergence, and the tree it already produced is
repaired in the same commit -- the codemod is idempotent against its own output,
so it cannot undo this itself.
2026-08-01 17:42:28 -07:00

50 lines
1.4 KiB
Cheetah

receivers:
prometheus:
config:
scrape_configs:
#__SCRAPE_CONFIGS__
processors:
# Shed load instead of buffering unbounded memory when Insights is unreachable.
memory_limiter:
check_interval: 1s
limit_mib: 512
spike_limit_mib: 128
batch:
exporters:
#__DEBUG_EXPORTER__
otlphttp:
# The otlphttp exporter appends /v1/metrics to `endpoint`, but Insights's
# public ingest route is /i/v1/metrics, so pin the per-signal path.
metrics_endpoint: '${env:INSIGHTS_HOST:-https://us.i.hanzo.ai}${env:INSIGHTS_INGEST_PATH:-/i/v1/metrics}'
compression: gzip
headers:
authorization: 'Bearer ${env:INSIGHTS_API_KEY}'
#__SENDING_QUEUE__
retry_on_failure:
enabled: true
extensions:
#__FILE_STORAGE__
health_check:
endpoint: 0.0.0.0:13133
service:
# Expose the collector's own metrics (scrape health, queue depth, drops)
# on :8888 so the agent is self-observable, the way vmagent exposes its.
telemetry:
metrics:
readers:
- pull:
exporter:
prometheus:
host: 0.0.0.0
port: 8888
extensions: [__SERVICE_EXTENSIONS__]
pipelines:
metrics:
receivers: [prometheus]
processors: [memory_limiter, batch]
exporters: [__PIPELINE_EXPORTERS__]