-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add filtering monitor list and status history by its status (UP|DOWN) #1971
Add filtering monitor list and status history by its status (UP|DOWN) #1971
Conversation
This functionality would be very useful! |
Co-authored-by: Adam Stachowicz <saibamenppl@gmail.com>
Co-authored-by: Adam Stachowicz <saibamenppl@gmail.com>
Co-authored-by: Adam Stachowicz <saibamenppl@gmail.com>
Will it be merged, @louislam ? |
It would be great if this could be merged! |
@louislam ping |
@louislam Any update on getting this merged? This is a pretty commonly requested feature. |
@louislam can we get this merged? |
@louislam - are you saying you'll merge it after you're able to tweak the UI, or you're asking @zolotarev to clean up his UI implementation? |
I would really like to have the option to group by status also ! It would be easyer to see what I need to fix :) Thanks ! |
Is there an update on this issue by any chance? |
It would be really great if can merge this with such a useful function |
+1 Would be great to have! |
i really need this feature 👍 |
Any update on this being merged? |
@sym0nd0 @I-Fun @R0GGER @AMSFauzi7869 @m3ki @ianaway Please refrain from posting |
@jeremyrnelson |
I absolutely don't understand why we are talking aesthetics over functionality... I bet a lot of people would want this now and fix border, margins, css later... It's getting really hard to manage. |
Our Contribution guidelines clearly state, that I completely see your frustrations, but fixing something in master is not feasible in a BDFL style project. |
I supported the project for a while until I realized that @louislam was completely overwhelmed and was far more concerned with adding all sorts of extra whiz-bang widgets than fixing some core functionality that larger users desperately need, and the UI completely falls apart with large numbers of alerts. That's certainly his right, but we gave up and ended up going back to Uptime Robot because it just works, where UptimeKuma just doesn't. It definitely looks pretty, but functionally it just doesn't scale. |
@jeremyrnelson consider forking? |
Yes, but the problem is I’m not a developer. I’d love to pay somebody to
fork it and just add a couple of features to make it usable for a large
number of monitors. If anyone is interested, DM me :)
On Wed, Jun 21, 2023 at 18:28 Pierre ***@***.***> wrote:
@jeremyrnelson <https://github.com/jeremyrnelson> consider forking?
—
Reply to this email directly, view it on GitHub
<#1971 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJRW5E4KP7AWKUPZ2E5F4DXMNYSVANCNFSM55SL672Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Jeremy
|
@jeremyrnelson I tried doing a fork last year, but it's a massive amount of work. We were using uptime-kume and after 200-300 hosts, it uses a ton of CPU for no reason. What I wanted to do was remove the useless junk that was added, and only keep the original idea of Ping, UDP, TCP, and HTTP checks. I ran into major issues trying to merge any of these Open Pull Requests because they have been ignored for so long that the amount of conflicts is massive. |
That does not surprise me at all. Honestly, very little has been added in
the last year of any fundamental benefit. It actually might be easier to
go back a year and start from there . Part of the reason I was attracted
to it in the first place was because of the simplicity and efficiency, but
that sort of got thrown out the window somewhere along the line.
On Wed, Jun 21, 2023 at 19:05 Juan Calderon-Perez ***@***.***> wrote:
@jeremyrnelson <https://github.com/jeremyrnelson> I tried doing a fork
last year, but it's a massive amount of work. We were using uptime-kume and
after 200-300 hosts, it uses a ton of CPU for no reason.
What I wanted to do was remove the useless junk that was added, and only
keep the original idea of Ping, UDP, TCP, and HTTP checks.
I ran into major issues trying to merge any of these Open Pull Requests
because they have been ignored for so long that the amount of conflicts is
massive.
—
Reply to this email directly, view it on GitHub
<#1971 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJRW5CJXGRPIVBDRNZBFGLXMN42BANCNFSM55SL672Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Jeremy
|
Please stick to the topic. If you have any ideas on how to improve a large amount of monitors, feel free to open a new pull request. For this pr, I had already commented on #1971 (comment). And as @CommanderStorm said, the black border looks weird especially in the light theme. |
Description
Add filtering monitor list and status history by its status (UP|DOWN)
Fixes #1585
Type of change
Checklist
(including JSDoc for methods)
Screenshots