GitLab-15-Breaking-Changes.md

@@ -130,9 +130,19 @@ grep `status_checks` /var/log/gitlab/gitlab-rails/api-json.log
 zgrep `status_checks` /var/log/gitlab/gitlab-rails/api-json.log.*
 ```
 
-If there's no hits, then the api isn't being used, so no impact.
+- If there's no hits, then the api isn't being used, so no impact.
+- If it is being used, identify affected users from the logs.
 
-If it is being used, identify affected users from the logs.
+#### fast-stats
+
+- [fast-stats top](https://gitlab.com/gitlab-com/support/toolbox/fast-stats) does a really good job summarising the log data:
+
+```shell
+zgrep -h `status_checks` /var/log/gitlab/gitlab-rails/api-json.log.* | ~/bin/fast-stats top -l 50
+```
+
+- that'll summarise just the log entries that are returned by grep, and provide you with the top fifty users, projects etc. 
+- it summarises the API paths, so if this grep finds API calls that it shouldn't have, fast-stats will be a more efficient way to see this.
 
 ---