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

[Uptime] Monitor list expanded row columns and most Recent error timestamp #50981

Closed
shahzad31 opened this issue Nov 18, 2019 · 4 comments · Fixed by #51935
Closed

[Uptime] Monitor list expanded row columns and most Recent error timestamp #50981

shahzad31 opened this issue Nov 18, 2019 · 4 comments · Fixed by #51935
Assignees
Labels
Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan v7.6.0

Comments

@shahzad31
Copy link
Contributor

shahzad31 commented Nov 18, 2019

Most recent error

we should include a timestamp for most recent error, especially since we are showing this data for checks that have an Up status as well. If my monitor is up and I'm still being shown the most recent error, I'd like to know if it was 30s ago or 3 days ago.
expanded_row_review

@shahzad31 shahzad31 added the Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability label Nov 18, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

@shahzad31
Copy link
Contributor Author

@katrin-freihofner can you please guide, how we should display timestamp for most recent error?

@katrin-freihofner
Copy link
Contributor

@shahzad31 I think we can just add it to the headline like:

Most recent error (30 min ago)

About the Url in the expanded row and in the table row/header...this will be gone with the new design.

@justinkambic
Copy link
Contributor

++ sounds good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test-plan v7.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants