[RFC] Add Monitoring Interface for External Logging Backends

Open
#1,213 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
observability

Research direction

The RFC names no files, tests, or existing entry points. Start by reviewing the repository’s current logging and training integration points, then clarify the scope and API for a backend-agnostic monitor with optional external integrations. Done means an agreed design and implementation plan; specific validation is not defined here.

Written by the indexing model from the issue text.

Description

🚀 The feature, motivation and pitch

Liger-Kernel provides a simple way to improve training throughput, but we need to manually implement logging to see these results while training.

A lightweight monitoring interface would:

  1. Make Liger's benefits visible in real experiments
  2. Help debug performance regressions across release versions

The integration can feature a common liger_kernel.monitor module with a backend agnostic interface that can enable adding external logging backends such as Weights and Biases, Trackio, Comet, etc. in a seamless manner. The external backends would be decoupled such that the backends would only be imported if they are installed in the user environment. This would also ensure that no external dependencies are added to the core dependency list.

Feel free to give feedback on this RFC on the scope of the API and its design.

Alternatives

No response

Additional context

No response

Dominant language
Python
Stars
6.7k
Forks
656
Avg merge
4d 12h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linkedin/Liger-Kernel

All issues in linkedin/Liger-Kernel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.