Closed amarbarot closed 4 years ago
@amarbarot thanks for this issue. I/we'll look into it this week. cc: @ricegi
@amarbarot follow up: your screenshot makes me think that this was run against an older version of the app. As of version 1.5.1, we've made a number of performance improvements, including moving the loading of underlying entities to the Detail screen. I've tested it against some significantly workloads and not generated errors. Could you verify which version of the application you're running. The current New Relic One Catalog version is Version 1.5.1 released on August 27, 2020
.
@tangollama ah!, The version I am running is the one we deployed to originally fix the issue in July, i think 1.1.7
So 1.5.1 fixes this issue, do you know if we have an entity limit with 1.5.1, can it load hundreds/thousands of entities without breaking?
@tangollama Ive downloaded 1.5.1 and its working a lot better, im going to attach 15 accounts worth of workloads and see how it performs, if we have no issues ill close this ticket.
I'm so happy :), the business value of these tool is very high.
Ok, GeoOps is performing fine. Im happy and closing the ticket.
Awesome. Thanks @amarbarot.
GeoOps can only seem to support up to 124 entities, if i increase the entity limit to 125 the map breaks, we need this limit increased to 10,000.
Below is an example of a map with 4 workloads attached, that have between them 124 entities, the map loads fine and no problems:
After adding one more entity the form no longer loads:
Steps to Reproduce
Expected Behaviour
Relevant Logs / Console output
Your Environment
Additional context