-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Remove map from Uptime details page #86485
Comments
Pinging @elastic/uptime (Team:uptime) |
Is it causing us an issue, and so we want to remove it? A use case I can imagine would be to see failures from clusters in specific regions, e.g. is the website only down to visitors from Europe? Wouldn't the map view make that easier to determine? |
Yes, it's a burden to maintain, and a fairly heavy dependency. I don't doubt that it has some utility, but it hardly seems worth it to maintain. The default view is a list of monitor locations by name, which in the example of 'europe' would be just as easy to determine, since you'd have a testing location named |
As discussed here this will be removed |
Ran locally, map is indeed gone. On a personal note, I'm happy to see this dependency go away as it was a pain to maintain and made our platform migration 5x as difficult as it could've otherwise been. |
The map view of monitor locations in the Uptime app doesn't provide much value vs. the list with availability and recency. I propose we consider removing it unless someone can name a use case that still makes it useful. The only value it adds is showing exact locations on a map, which is useful if the location names are not descriptive enough. I think this is probably pretty rare.
CC @drewpost @katrin-freihofner @paulb-elastic
The text was updated successfully, but these errors were encountered: