summary refs log tree commit diff
path: root/develop/admin_api/statistics.html
diff options
context:
space:
mode:
authorclokep <clokep@users.noreply.github.com>2023-05-10 13:02:53 +0000
committerclokep <clokep@users.noreply.github.com>2023-05-10 13:02:53 +0000
commit3631b3504ba1b825fb66cb210b3aaaf9e543b594 (patch)
treeaaf1fee001f840b1f2a826093f7b1585cb48250a /develop/admin_api/statistics.html
parentdeploy: ab4535b6082db97e8c48a69ea6674fe3b7c5e956 (diff)
downloadsynapse-3631b3504ba1b825fb66cb210b3aaaf9e543b594.tar.xz
deploy: 7e6ad62c49104e5a17d1d35fe4c743b9fd7cd31d
Diffstat (limited to 'develop/admin_api/statistics.html')
-rw-r--r--develop/admin_api/statistics.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/develop/admin_api/statistics.html b/develop/admin_api/statistics.html

index 16f046d5e4..4bf39652a8 100644 --- a/develop/admin_api/statistics.html +++ b/develop/admin_api/statistics.html
@@ -231,7 +231,7 @@ they are taking.</p> which means that the returned information can vary widely from reality. However, it should be enough to get a rough idea of where database disk space is going.</p> <p>The API is:</p> -<pre><code>GET /_synapse/admin/v1/statistics/statistics/database/rooms +<pre><code>GET /_synapse/admin/v1/statistics/database/rooms </code></pre> <p>A response body like the following is returned:</p> <pre><code class="language-json">{