Skip to content

fix: say what seeds a HyperDX team, not the engine's service token - #190

Merged
catinspace-au merged 2 commits into
mainfrom
fix/68-seed-docs
Sep 29, 2026
Merged

catinspace-au merged 2 commits into
mainfrom
fix/68-seed-docs

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

The HyperDX section of docs/configuration.md, and the comment on DFE_HYPERDX_ENABLED in docker-compose.yml, said the engine's service token seeds the default team with its connection and sources before anyone logs in. It never did. The engine gives the service identity no ClickHouse connection, so its team (DFE_HYPERDX_TEAM) stays empty.

  • a team is seeded from the engine's answer for its members, on their first login
  • the retry on a later request lands with hyperi-io/dfe-hyperdx#106, and the doc says so
  • default-sources.json seeds nothing in oidc-proxy mode, only header-dev

Checked on a local stack with the rc.14 pins: team dfe had 0 connections and 0 sources on v0.2.7, dfe-admins was seeded at the admin's login.

Refs hyperi-io/dfe-hyperdx#68

The docs and a compose comment said the engine's service token seeds the default team with its connection and sources before anyone logs in. It never did: the engine gives the service identity no ClickHouse connection, so that team stays empty. A team is seeded from the engine's answer for its members, on their first login.
HyperDX never seeds from the service token at all, so that is the reason to give, not what the engine would answer if it were asked.
@catinspace-au
catinspace-au merged commit d63a743 into main Sep 29, 2026
7 checks passed
@catinspace-au
catinspace-au deleted the fix/68-seed-docs branch September 29, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant