- Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
- Used code blocks with ``` to format my code examples like JSON or logs properly.
I’m submitting a…
- Regression (a behavior that stopped working in a new release)
- Bug report
- Performance issue
- Documentation issue or request
Current behavior**
We are having too high API calls.
What does the anonymous call mean in Squidex?
Our dev mentioned that there are many calls for web, for sure, but he always see anonymous calls from api performance too much so it shows that these calls creating these calls.We noticed that with 567 active users presentes on GA, we are at 50k api calls, is that possible that someone is pinging our api outside? Can you please revise? We will cache APIs but it won’t be enough probably, because it is an absurd API call count. We need to find an answer and solution.
Expected behavior
We are expecting less api calls since we have not that much of visitors on our website. That much api calls leads to not consistent responses from squidex.
Minimal reproduction of the problem
Please, check our API calls dashboard to see the peaks.
I can share our traffic stats per day, and all the information you might need to compare that we don’t have such a traffic to create those API peaks.
Environment
App Name:
travel-diaries
- Self hosted with docker
- Self hosted with IIS
- Self hosted with other version
- Cloud version
Version: 7.0.0.0
Browser:
- Chrome (desktop)
- Chrome (Android)
- Chrome (iOS)
- Firefox
- Safari (desktop)
- Safari (iOS)
- IE
- EdgeOthers:
What does the anonymous call mean in Squidex?
Anonymous API calls are usually assets. But they are only counted as 0.1 API call.
.We noticed that with 567 active users presentes on GA, we are at 50k api calls
50000 / 567 is 88 page views, so I think it is not unrealistic. You really have to check the logs. Internal API calls from the frontend also count into that. There is nothing i can do right now. Have yo used the CLI as mentioned before. You would get this result:
Most used requests:
-------------------------------------------------------------------------------------------------
| Path | Count |
-------------------------------------------------------------------------------------------------
| POST /api/content/travel-diaries/graphql | 729547 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/sharediary/99d00041-c135-4328-95e5-1d210b883109 | 417734 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/blog-categories/ | 178916 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/faq-items/ | 110376 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/subcategories/ | 99139 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/reviews/ | 98545 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/page-home/5ae975cc-9f79-494e-8625-9849d4d8aa0d | 98441 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/shareblog/1bd7d4ef-b55d-47fd-9d63-5b06355ea1a7 | 61050 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/footer | 57921 |
-------------------------------------------------------------------------------------------------
| GET /api/apps/travel-diaries/history | 39662 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/page-user-terms/d58d086f-f43e-4e24-a92a-9fd22d6e7ae4 | 31122 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/page-terms/d24fe352-7837-489e-a807-bf527385af3a | 23145 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/team-members/0c9100cf-6f72-4db0-a857-13097b00f9bc | 17316 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/team-members/dbaff839-06bf-4468-884a-d5f906606b87 | 9387 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/team-members/130bf884-4f25-49ed-a62c-4d254bd10dab | 6443 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/team-members/8aa52037-01e3-40ed-8e65-5c38bc9c2b50 | 5327 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/team-members/43961443-1d06-40f3-9c99-970ca5e77a30 | 5162 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/blog-category-tags/ | 4533 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/team-members/b95f6d8b-d81a-4de6-a710-4bd7c908567f | 2930 |
-------------------------------------------------------------------------------------------------
| GET /api/content/travel-diaries/blog-categories/7e65fd3e-36fe-4ecf-abae-1d993a1b12bd | 2860 |
-------------------------------------------------------------------------------------------------
Most of those things usually do not change. I have no idea what happens in the first request, but everything except the first one is actually cacheable.
1 Like