lablup / lablup/backend.ai

Explore Vector as a log and metric exporter

Open
#2,018 0 comments 0 reactions 1 assignee Assigned to @hoyajigi View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
15h 13m
Merged PRs (30d)
368

Description

[Vector](https://vector.dev/) (made by Datadog) is a high-performance observability pipeline tool, which can collect and process events, logs, and metrics. It's written in Rust and some of my friends in "big techs" reported that it works successfully in very large-scale deployments.

https://vector.dev/docs/about/concepts/

Let's inspect how we can integrate this into our platform, particularly in on-premise customer sites. Since there are multiple "vector sink" implementation, we could attach Datadog in the cloud while attaching other open-source dashboards in the on-prem setups.

- We could provide some "vector source" configuration samples (e.g., capturing the stderr stream of service daemons).
- We could write additional logging backends in `ai.backend.common.logging` to feed structured logs to the vector pipeline directly.
- We could extend our stats subsystem in `ai.backend.agent.stats` to feed metrics to the vector pipeline. If we write our own prometheus exporter interfaces, we could reuse them for the vector sources.
- We could extend #1639 and our event bus to feed health check events to the vector pipeline.
- We could provide some "vector transform" configuration samples to detect anomalies in the manager and agents.
- We could update our internal dahsboard project to take the role of "vector sinks" to accept and display the processed observability data.
- Q: Could we use Graylog as a sink? What about Grafana Loki as the log viewer?
(taken from https://vector.dev/docs/setup/deployment/)

JIRA Issue: BA-129

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.