This repository has been archived by the owner on May 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Motion telemetry through Singularity #174
Comments
xinaxu
added a commit
to data-preservation-programs/singularity
that referenced
this issue
Oct 23, 2023
Offer an API to set the identity as a global variable in the database. This identity is only settable via API call. All telemetries published will include this identity as part of payload. This is the first step for filecoin-project/motion#174
xinaxu
added a commit
that referenced
this issue
Oct 23, 2023
Context: - #174 Previous steps - data-preservation-programs/singularity#398 - data-preservation-programs/singularity-metrics@46bc0d3 Next step: - Create Grafana dashboard with tagged motion telemetry
xinaxu
added a commit
to data-preservation-programs/singularity
that referenced
this issue
Oct 24, 2023
Due to how Motion docker compose is structured, the best way to set the identity to motion is through the admin init CLI command. This is part of filecoin-project/motion#174
xinaxu
added a commit
that referenced
this issue
Oct 25, 2023
Follow-up of #177 Motion container starts after other Singularity container starts hence setting identity inside motion container does not take effect until the user restart the docker compose. To address above issue, we can set the identity to Motion during Admin init script. Tested end to end and see data reflected on Dashboard https://dataprograms.grafana.net/d/f49ba403-a767-4243-af44-607dec1e7100/usage?orgId=1 fixes #174
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Singularity already collects metrics about
Motion would like to have visibility into who is using and the volume of data onboarded.
The ask is to make Singularity support a way to tag the metrics with Motion
The text was updated successfully, but these errors were encountered: