Disroot
/
zabbix-scripts
5
0
Fork 1
Code Pull Requests Projects Releases Activity

get for 10 biggest repo in forgejo #15

Merged
meaz merged 2 commits from forgejo_biggest_repo into main 2024-01-05 10:47:23 +01:00
Conversation 3 Commits 2 Files Changed 1 +8 -1
meaz commented 2023-12-06 11:32:15 +01:00
Owner
Copy Link

I added that line to get the 10 biggest repo. I'm not sure it is the smartest way to use echo "git_biggestrepos ${GIT_BIGGESTREPOS}" >> /tmp/git_stats coz it would be displayed like this:

git_biggestrepos  repostest1       | 6936 MB        | user1
 repostest2       | 5212 MB        | user2
 repostest3 | 5039 MB        | user3

So I don't know how to get this in monitoring to work...

I added that line to get the 10 biggest repo. I'm not sure it is the smartest way to use `echo "git_biggestrepos ${GIT_BIGGESTREPOS}" >> /tmp/git_stats` coz it would be displayed like this: ``` git_biggestrepos repostest1 | 6936 MB | user1 repostest2 | 5212 MB | user2 repostest3 | 5039 MB | user3 ``` So I don't know how to get this in monitoring to work...
muppeth was assigned by meaz 2023-12-06 11:32:16 +01:00
meaz added 1 commit 2023-12-06 11:32:16 +01:00
muppeth added 1 commit 2024-01-04 00:13:50 +01:00
muppeth commented 2024-01-04 00:15:55 +01:00
Owner
Copy Link

With top 10 biggest repos, (and I would add top 10 repo owners) I would not push the result directly to zabbix as it will be hard to follow and create a trigger. I have pushed solution to formating and added top 10 repo owners. It's hard to make a trigger for this kind of data, perhaps we could just trigger if the data changes, so that if any of the top 10 changes we will get a trigger and then we can check what's up. Maybe it will not be happening too much often.

With top 10 biggest repos, (and I would add top 10 repo owners) I would not push the result directly to zabbix as it will be hard to follow and create a trigger. I have pushed solution to formating and added top 10 repo owners. It's hard to make a trigger for this kind of data, perhaps we could just trigger if the data changes, so that if any of the top 10 changes we will get a trigger and then we can check what's up. Maybe it will not be happening too much often.
meaz changed title from WIP: get for 10 biggest repo in forgejo to get for 10 biggest repo in forgejo 2024-01-04 18:25:31 +01:00
meaz commented 2024-01-04 18:26:46 +01:00
Author
Owner
Copy Link

sounds good to me. Shall I merge this then?

sounds good to me. Shall I merge this then?
muppeth approved these changes 2024-01-05 09:50:32 +01:00
muppeth commented 2024-01-05 09:51:20 +01:00
Owner
Copy Link

Yes we could merge and then see what we do with the data on zabbix side or whether we want to also send out reports to xmpp or something. but thats another unrelated to this repo thing.

Yes we could merge and then see what we do with the data on zabbix side or whether we want to also send out reports to xmpp or something. but thats another unrelated to this repo thing.
meaz merged commit 1371b2c62c into main 2024-01-05 10:47:23 +01:00
meaz deleted branch forgejo_biggest_repo 2024-01-05 10:47:23 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
muppeth
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
muppeth
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/zabbix-scripts#15
No description provided.
Delete Branch "forgejo_biggest_repo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?