-
Notifications
You must be signed in to change notification settings - Fork 9
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
Gather information about the requests to and from RC API #1157
Comments
Based on Lumen documentation, there are no statistics about cache usage, but we could generate them by using the EventServiceProvider. |
More monitoring from Elastic Cloud can be found here : https://3b83e4a3efda4f5e8c2f8f2ec07c0fc2.us-east-1.aws.found.io:9243/app/monitoring#/elasticsearch/nodes |
Today from 1am to 2am (GMT) there was a spike of requests to Elasticsearch(table shows hours using GMT+2 timezone): Requests from AWS for that time frame have been centralised here: https://docs.google.com/spreadsheets/d/1mhHmy6n9m3PMY-BLzLhDXz3jFL6FECRJ8sW5oE09S18/edit#gid=153453992 |
Yesterday from 3pm to 4pm there was another spike of requests. |
To obtain the above data, I have downloaded the AWS ALB logs(from S3:
The resulted file was then imported to GDrive. |
On the 23rd of December, between 5pm and 6pm, the following requests have been made: Data has been gathered here: https://docs.google.com/spreadsheets/d/1mhHmy6n9m3PMY-BLzLhDXz3jFL6FECRJ8sW5oE09S18/edit#gid=296562686&fvid=1368567753 |
|
Why
To reduce the number of calls to Elasticsearch we need to understand who triggers them.
What
Notes
The text was updated successfully, but these errors were encountered: