axiomhq/axiom-loki-multiplexer

A push interface to Axiom via Loki endpoint.

Owned by Axiom

View on GitHub ↗Jump to charts ↓

axiomhq/axiom-loki-multiplexer is written in Go and was last pushed on Mar 7, 2023. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 9 minutes ago
Added to GitGenius on October 12th, 2026
Created on January 6th, 2021
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 2
Total Stargazers: 5 (+0)
Total Subscribers: 1 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Axiom Loki Multiplexer is a log aggregation adapter that enables pushing logs to Axiom through a Loki-compatible endpoint.

The tool solves the problem of integrating Axiom with existing Loki-based logging infrastructure. It works by accepting logs via the Loki push API and forwarding them to Axiom, allowing users to leverage their current Loki clients and agents like Promtail without requiring separate integrations. This approach bridges two logging systems, letting teams use Axiom as a backend while maintaining compatibility with Loki's established protocol and tooling.

The multiplexer suits organizations already running Loki or Promtail who want to adopt Axiom for log storage and analysis without rewriting their logging pipelines. It is particularly valuable for teams seeking to consolidate logging infrastructure or migrate gradually from Loki to Axiom by running both systems in parallel. The tool preserves the investment in existing Loki configurations while opening access to Axiom's capabilities.

Development activity shows consistent engagement with the codebase through regular commits addressing bug fixes and feature improvements. The project maintains responsiveness to issues and pull requests, indicating active maintenance. Code quality appears prioritized, with attention given to testing and documentation updates alongside functional changes.