louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
52.56k stars 4.73k forks source link

Add More Details in status page #2933

Open ShadowGaming100 opened 1 year ago

ShadowGaming100 commented 1 year ago

⚠️ Please verify that this feature request has NOT been suggested before.

🏷️ Feature Request Type

Other

🔖 Feature description

Updates of the Status Page

Add the following features

  1. Show incident history

    example

    ![FFBB57BC-14E0-4419-A44C-7B5CC3DEDBDE](https://user-images.githubusercontent.com/81495140/225323470-b5c517be-d95f-4538-9fac-2f78c3d7862e.jpeg)

    • If show empty incidents is disabled hides all empty incidents, able to change this settings global or by status page
    • Able to change how incidents are groups, by month or by day
    • It shows only of 6 months if incidents are divided by month else if divided by day shows only of the current month
  2. Below the monitor able to add graphs or chart

    example

    ![graphs](https://user-images.githubusercontent.com/81495140/225323175-dc688d61-2c0d-4207-8118-12bb02e4297a.jpeg)

    • Able to add specific number of graphs or charts
    • Show the graph in day, week, and month
  3. monitor and bar chart updates

    examples

    ![3482DB8B-BA2C-4374-B804-8A545031C4D7](https://user-images.githubusercontent.com/81495140/225328555-4a677e64-acba-4060-8f51-b936e2913400.jpeg) ![0F85FCBE-EA69-4FCD-93D9-E1C4B5D319EF](https://user-images.githubusercontent.com/81495140/225333291-406740ff-1d8e-4d7e-9610-b72a34fd78cf.png)

    • update the bar chart, so when you click it it shows the time and if there is any incident it shows if now shows no incident recorded
    • able to add custom monitors description

Create New Page (maybe)

  1. If click in a monitor and shows the following information

    • see uptime, ping, bar chart
    • Below shows a graph (user choice to add)
    • show incidents of specific monitor, refer to number one for more information about incidents
  2. When click in an incident

    example

    ![6A30BAD8-0DF4-4D0F-B546-3792ABB62FC6](https://user-images.githubusercontent.com/81495140/225326000-8c9bed42-db93-4ea1-a811-c124462bc9b7.jpeg)

    • shows developer comments

I will still update this

✔️ Solution

in my case, we can update the current status page with the following things:

And this may involve making a new page:

❓ Alternatives

No response

📝 Additional Context

in Status page In Incident update
C720A702-784E-4062-973E-7A6E0CC23F4D 5D306598-2CE2-4F58-8846-ACD2AADC7837
ShadowGaming100 commented 1 year ago

And refer for this issue that can be added in incident page #2926

ShadowGaming100 commented 1 year ago

I have more ideas but couldn’t add when I created this post

ShadowGaming100 commented 1 year ago

Refer this issue even #2756

ShadowGaming100 commented 1 year ago

My idea has been created by someone in #2943

tkbstudios commented 1 year ago

The incident's history and current ping and all the other stuff mentioned here are amazing! This will make everyone use uptime kuma for the same features as Atlassian Status Pages but because uptime kuma is free, even more people will talk about it!

ShadowGaming100 commented 1 year ago

can add this even https://discordstatus.com/uptime

ShadowGaming100 commented 1 year ago

to uptime kuma for real. The incidents history and current ping and all the other stuff mentioned here are amazing! This will make everyone use uptime kuma for the same features than Atlassian Status Page

have more features coming soon for status and incidents

Aetherinox commented 10 months ago

Thank you for working on this stuff. I found Uptime Kuma today, and the only thing that turned me off to it was the very barebone status page. Slightly bigger bars would be nice (but that can be done via CSS), but having graphs, and maybe the "Operational" or "Down" text would be awesome.

Sorry for butting in, just wanted you to know there's high interest in this.

CommanderStorm commented 10 months ago

@Aetherinox Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done how by whom. We use 👍🏻 on issues to prioritise work, as always: Pull Requests welcome.

https://github.com/louislam/uptime-kuma/pull/1253 is currently quite deadlocked, as it was created before multiple status pages were a thing, had changes to the database schema which were not discussed previously and is now a brutal rebase behind master. See https://github.com/louislam/uptime-kuma/pull/1253#issuecomment-1409899850

If you/someone else wants to contribute a second version of this incident system, please feel free. Also note that a +4k added lines is absolutely unreviewable. Please stick with smaller subfeatures first.

mattholy commented 4 months ago

incident tracking is very useful when you are telling users what are we doing now.

like statuspage of Atlasian, or Cachet.

tkbstudios commented 4 months ago

Yeah exactly, this could be pretty useful for uptime kuma

ShadowGaming100 commented 2 months ago

i am shocked my issue has not been still closed after a year

thanks for everyone loving the idea

tkbstudios commented 2 months ago

Marking the last comment as spam was unnecessary, the OP thanked everyone, that is NOT spam.

CommanderStorm commented 2 months ago

@tkbstudios Moderation decisions are always a gray area. Especially, what is considered spam. My measure of spam is "Is this productive (as in moving the issue forward), relevant to the issue and written in a productive tone?"

Spam marking was mostly because I did not want to respond to this passive-aggressive remark and because this said comment is not moving the issue forward. Jea, might have been overly sensitve.. 🤷🏻‍♂️

I am shocked my issue has not been still closed after a year

Longer answer: If your issue contains 4 different major sub-issues it is unsurprising to me that it will take a longer time.

I am a bit tired of this demand-attitude: Open source is delivered “as is” by volunteers. This is not a megacorp which has full-time developers. => no guarantees (it might if another dev has the time for it, it might not) that an issue is implemented in any timeframe. See https://github.com/louislam/uptime-kuma/pull/1253#issuecomment-1924191591 the relevant part of the discussion about this issue.

TL;DR: If you want it implemented, our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md