Skip to content

feat: upgrade Vector to 0.55.0 and add optional Axiom regional edge support#75

Open
XXMOHAMED012 wants to merge 1 commit into
superfly:mainfrom
XXMOHAMED012:main
Open

feat: upgrade Vector to 0.55.0 and add optional Axiom regional edge support#75
XXMOHAMED012 wants to merge 1 commit into
superfly:mainfrom
XXMOHAMED012:main

Conversation

@XXMOHAMED012

Copy link
Copy Markdown

What and why

The current Vector image (0.29.1) predates Axiom's regional edge support, so the Axiom sink always routes data to the US endpoint — even when a user's organization is on the EU deployment. This makes fly-log-shipper unusable with Axiom's eu-central-1 edge dataset.

Vector 0.52.0 added a region field to the Axiom sink that routes ingest traffic to the correct edge domain. This PR bumps Vector to 0.55.0 and exposes that field as an optional AXIOM_REGION secret.

Changes

  • Dockerfile — bumps timberio/vector:0.29.1-debian0.55.0-debian
  • vector-configs/axiom.toml — adds an optional region line using the existing shell templating pattern; the line is omitted entirely when AXIOM_REGION is unset, so existing users see no change in behaviour
  • README.md — documents AXIOM_REGION in the Axiom secrets table

Usage

For EU users, set:

fly secrets set AXIOM_REGION=eu-central-1.aws.edge.axiom.co

Leave it unset to keep the existing US endpoint behaviour. See [Axiom edge deployments](https://axiom.co/docs/reference/edge-deployments) for all available values.

Backwards compatibility

No breaking changes. The AXIOM_REGION variable is fully optional, and the Vector 0.55.0 image is compatible with all existing sink configurations in this repo.

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