You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those queries should be generic, so that admins do not need to modify them and can just run them monthly or every 3 months or so, the change always collects the data between 5 years (and forever) and the first day of the month where the query is run.
Should the admin create the instance folders (fr, eu, org, au, etc) manually or is the code directly capturing that?
How do we know who has access to "Galaxy Admin Stats Account"? Is there a link to github pages for the main instances?
Currently we need to run the query manually or ask admins to do it (we got the contacts), for a while I try to set it up automatically, see https://github.com/usegalaxy-eu/issues/issues/510: with this query we will try to make it work on EU (run query monthly, export to Graphana, that gives us an API endpoint to pull it periodically with CoDex) and then convince admins of other servers to implement the same logic.
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
Needs to be run via the Galaxy Admin Stats Account
Needs to be run via the Galaxy Admin Stats Account
For people who do not have access to the Galaxy Admin Stats Account :
1. Reach out to an admin
2. Provide them with the SQL queries (or a link to this page)
Once the files have been generated :
1. Create a new folder in the [folder sources/data/usage_stats of the galaxy_codex repository](https://github.com/galaxyproject/galaxy_codex/tree/main/sources/data/usage_stats)
2. Name the folder 'usage_stats_YYYY.MM.DD'
3. Within this folder, create a subfolder indicating the instance where the data are coming from (eu, fr, org, or org.au)
Ok, I don't have access to usegalaxy-eu issues (they are not public), so it was harder to get the context.
So the current process is to reach out to an admin, give them the SQL queries, receive the files and drop them in the codex?
sorry, I missed, that you do not have access to our issues. yes, this is the current manual way. Would be great to get automatic access.
Great! I've tried to include a short protocol to explain that to people coming to this page (until we get an automated process)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since users ask for this more and more, we should try again to automize it: https://github.com/usegalaxy-eu/issues/issues/510
Those queries should be generic, so that admins do not need to modify them and can just run them monthly or every 3 months or so, the change always collects the data between 5 years (and forever) and the first day of the month where the query is run.