You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are many projects in Sentry, the process of collecting metrics can take a long time. In some cases, it may be interesting to point out only projects that have already been mapped and that need special attention. In addition, there is apparently a limit of 100 in the counters, where I cannot see more than 100 issues of the same project and not more than 100 projects.
I am grateful if you can help me and if I develop something locally, I share with you to evaluate.
The text was updated successfully, but these errors were encountered:
For the 100 items limitation, there is a paging feature in the API, see https://docs.sentry.io/api/pagination/
So, if only 1 project is requested it may make sense to retrieve more than 100 entries. I think that it already takes quite long to retrieve all the data if you have multiple projects. So maybe it will work for more entries for 1 project (lets assume 500 or 1000) but there will be a limit anyway as requesting large amounts (lets say 10k issues) will lead to a timeout at a certain point.
If there are many projects in Sentry, the process of collecting metrics can take a long time. In some cases, it may be interesting to point out only projects that have already been mapped and that need special attention. In addition, there is apparently a limit of 100 in the counters, where I cannot see more than 100 issues of the same project and not more than 100 projects.
I am grateful if you can help me and if I develop something locally, I share with you to evaluate.
The text was updated successfully, but these errors were encountered: