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

Add cache to /mapping/entity endpoint to improve loading experience for PagerDutyPage #79

Open
t1agob opened this issue Jul 24, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@t1agob
Copy link
Contributor

t1agob commented Jul 24, 2024

Is your feature request related to a problem? Please describe.
The mapping/entity endpoint exposed by the backend component builds a list of all mappings between services and Backstage entities. Depending on the number of PagerDuty Services this might take a long time.

In #75, @alpinweis reported than in their case with over 200 services it takes consistently 10-15 seconds to load the page.

Describe the solution you'd like
I would like the performance of this endpoint to be improved drastically otherwise the user experience is not great.

There are users with a lot more services across several PagerDuty accounts and they cannot wait indefinitely for the page to load. This information needs to be cache because most of it is fairly static.

Describe alternatives you've considered
At this point in time there is no other option than to wait for the page to load.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Under review
Development

No branches or pull requests

1 participant