Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Status from Monitoring #532

Closed
wants to merge 1 commit into from

Conversation

Rabenherz112
Copy link
Contributor

@Rabenherz112 Rabenherz112 commented Sep 10, 2023

It appears that Status doesn't qualify as a sysadmin solution.

Status is a simple, lightweight system monitoring app for small homeservers running Linux.

I submitted a pull request to relocate it to the "awesome-selfhosted" repository instead.

Not a sysadmin tool
@nodiscc
Copy link
Collaborator

nodiscc commented Sep 12, 2023

In https://github.com/awesome-selfhosted/awesome-selfhosted-data/blob/master/tags/personal-dashboards.yml the description states "Dashboards for accessing information and applications", so the "Monitoring" section is actually more appropriate.

See also awesome-selfhosted/awesome-selfhosted#3497 which is the reason why Status was added to awesome-sysadmin/Monitoring in the first place.

@Rabenherz112
Copy link
Contributor Author

I agree that it appears to be a better fit for a Monitoring Tag compared to the other Dashboards listed in the awesome-selfhosted collection. However, I'm still uncertain about the use case for this application from a sysadmin's standpoint. When I think of sysadmin monitoring solutions, I think of something like Netdata, but there are many other solutions like 'Status' such as Dashdot or Linux-Dash. So, there is no reason to just remove 'Status' since they all serve the purpose of monitoring the health of a server.

I should have checked before there are similar software like Status, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants