arch/vrchat-prometheus-adapter
1
0
Fork 0
Code Pull requests Packages 1 Activity Actions
Budget VEMS.
29 commits 1 branch 0 tags 96 KiB
  • Rust 97.4%
  • Dockerfile 2.6%
Find a file
Exact
Gabriel Simmer f746a3d6d6
All checks were successful
Build and Push vrchat-prometheus-adapter / build-arm64 (push) Successful in 26s
Details
Build and Push vrchat-prometheus-adapter / build-amd64 (push) Successful in 2m19s
Details
Build and Push vrchat-prometheus-adapter / merge (push) Successful in 46s
Details
Use Containerfile, remove Nix Flake
2025-03-12 09:48:17 +00:00
.forgejo/workflows Use Containerfile, remove Nix Flake 2025-03-12 09:48:17 +00:00
grafana Add additional metrics to example dashboard 2023-10-24 13:39:50 +01:00
src Use Containerfile, remove Nix Flake 2025-03-12 09:48:17 +00:00
.containerignore Use Containerfile, remove Nix Flake 2025-03-12 09:48:17 +00:00
.envrc Initial commit of proof of concept. 2023-10-20 22:16:33 +01:00
.gitignore Use Containerfile, remove Nix Flake 2025-03-12 09:48:17 +00:00
Cargo.lock Clean up flake.nix, add logging crates 2023-11-17 11:29:03 +00:00
Cargo.toml Clean up flake.nix, add logging crates 2023-11-17 11:29:03 +00:00
Containerfile Use Containerfile, remove Nix Flake 2025-03-12 09:48:17 +00:00
LICENSE Initial commit of proof of concept. 2023-10-20 22:16:33 +01:00
README.md Switch to fetching instances from group 2023-10-21 19:25:06 +01:00

README.md

VR Event Tracker

Adapter for VRChat API instance data and VRCDN API to Prometheus metrics.

Very budget version of VEMS, which can be viewed as a more complete solution. This is mostly for fun and learning. A dashboard is provided in grafana/dashboard.json.

Not a lot of metrics are collected at the moment. Just the ones I care about.

Configuration

Configuration is done with a config.toml file with the following format:

group = "group_7f23c663-e3c5-408f-bfb3-02b164f9e921"
vrcdn = "vrcdn_stream_name"

Instances will be retrieved from the group.

Runs on port 6534, on all interfaces. May be configurable in the future.

You will need to set the VRCHAT_AUTH_TOKEN environment variable to authenticate with VRChat's API. This isn't technically recommended and a more robust authentication system (see: correct) should be considered for serious use (see: VEMS).