Monitor: add history logs, either to emails or in dashboard.

[macmanx2]

Site owners receive Monitor emails, and some delete them. This isn't a very convenient way to share the "big picture" of what could be consistent server downtime or an overall failing server.

If we could find a way to log downtime reports for a particular site for just a 24-hour period, and include those historical downtime dates/times from the 24-hour period in the Monitor email, we will not only make the "big picture" easier to digest, we'll also provide something that is far more useful for the hosting provider to investigate.

Note that I'm not advocating the creation of a developer-resource-intensive UI or Dashboard for the Monitor itself, I'm just advocating 24-hour logging and reflection of that log in the Monitor emails.

I consider this issue somewhat of companion to #2796 but a bit lower priority, hence the separate issue.

[kraftbj]

I think the idea of a "audit log" for a site via wp.com would be really interesting. Monitor, by definition, means we can't rely on the JP site to log anything and the site on the wp.com side is the best "storage" place we have. Whether we display it via wp.com itself or via e-mail would be interesting.

[samhotchkiss]

This is definitely something that is being thought about, at the present time we don't store any of this data.

[jeherve]

Related:

I would love to see the number or times/length of time my site has been down on my dashboard. Some stats surrounding downtime would be great. Cheers!

2846087-t

[jeherve]

Related:

https://twitter.com/Markus64/status/940677448303300609
https://twitter.com/Markus64/status/940681544154406912

[saboarpad]

Related:
https://wordpress.org/support/topic/where-can-i-check-downtime-history-of-the-jetpack-monitor/#post-9845800

[jeherve]

Also suggested in 927566-zen

[stale]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[macmanx2]

Still valid, since it's an Enhancement request. I wonder if we should make the bot ignore those?

[jeherve]

From #10790

Is your feature request related to a problem? Please describe.

It would be best to provide downtime so all WordPress admins can see them. Also it would be best to see a history of these easily rather than depending on email.

Describe the solution you'd like

A downtime monitor dashboard.

Describe alternatives you've considered

No easy way to achieve using existing email approach.

[awayshops]

I would recommend bumping this to a higher priority. It seems to me that the dashboard feature, I proposed, would be another compelling reason to use Jetpack. Frankly, it's hard for me to understand how anyone could think otherwise - I must be missing something... Either, it's hard to do OR the data is not definitive enough? Perhaps your worried about incorrectly identifying downtime due to Internet traffic problems? Is it too hard of a nut to crack? I'm curious and would like to understand the reason it's not being pursued.

[jeherve]

I'm curious and would like to understand the reason it's not being pursued.

@jawhalen8463 We're currently not working on the Monitor feature; we've been focussed on other areas of Jetpack lately. However, when we come back around and give the Monitor feature some attention, this issue will definitely be under our radar!

[stale]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[stale]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[mayrsascha]

Hey stale bot, I think this is still relevant... Or maybe there is even a better place for this feature request like on a roadmap if that exists...