The config.cloudflare_hostnames setting currently filters Cloudflare Web Analytics to specific hostnames — useful for excluding API traffic and isolating UI activity. In our setup, these hostnames directly correspond to slices, which are already known to the backend.
Proposal:
Automatically populate cloudflare_hostnames based on the slices, unless the setting is explicitly configured. This avoids requiring redundant config and keeps analytics aligned with actual UI structure.
Behavior:
If config.cloudflare_hostnames is unset → derive hostnames from slices.
If config.cloudflare_hostnames is set → use as-is.
The
config.cloudflare_hostnamessetting currently filters Cloudflare Web Analytics to specific hostnames — useful for excluding API traffic and isolating UI activity. In our setup, these hostnames directly correspond to slices, which are already known to the backend.Proposal:
Automatically populate cloudflare_hostnames based on the slices, unless the setting is explicitly configured. This avoids requiring redundant config and keeps analytics aligned with actual UI structure.
Behavior:
If config.cloudflare_hostnames is unset → derive hostnames from slices.
If config.cloudflare_hostnames is set → use as-is.