forgejo/templates/admin/stats.tmpl

{{template "admin/layout_head" (dict "ctxData" . "pageClass" "admin monitor")}}
<div class="admin-setting-content">
	<h4 class="ui top attached header">
		{{ctx.Locale.Tr "admin.dashboard.statistic"}}
	</h4>
	<div class="ui attached table segment">
		<table class="ui very basic striped table unstackable">
			{{range $statsKey := .StatsKeys}}
			<tr>
				<td width="200">{{$statsKey}}</td>
				<td>{{index $.StatsCounter $statsKey}}</td>
			</tr>
			{{end}}
		</table>
	</div>
</div>
{{template "admin/layout_footer" .}}
Use a separate admin page to show global stats, remove `actions` stat (#25062) Before, Gitea shows the database table stats on the `admin dashboard` page. It has some problems: * `count()` is quite heavy. If tables have many records, this blocks loading the admin page blocks for a long time Some users had even reported issues that they can't visit their admin page because this page causes blocking or `50x error (reverse proxy timeout)` * The `actions` stat is not useful. The table is simply too large. Does it really matter if it contains 1,000,000 rows or 9,999,999 rows? * The translation `admin.dashboard.statistic_info` is difficult to maintain. So, this PR uses a separate page to show the stats and removes the `actions` stat. ![image](https://github.com/go-gitea/gitea/assets/2114189/babf7c61-b93b-4a62-bfaa-22983636427e) ## :warning: BREAKING The `actions` Prometheus metrics collector has been removed for the reasons mentioned beforehand. Please do not rely on its output anymore. 2023-06-03 17:03:41 +03:00			`{{template "admin/layout_head" (dict "ctxData" . "pageClass" "admin monitor")}}`
			`<div class="admin-setting-content">`
			`<h4 class="ui top attached header">`
Backport ctx locale refactoring manually (#27231) (#27259) (#27260) Backport #27231 #27259 manually --------- Co-authored-by: delvh <dev.lh@web.de> 2023-09-25 16:15:51 +03:00			`{{ctx.Locale.Tr "admin.dashboard.statistic"}}`
Use a separate admin page to show global stats, remove `actions` stat (#25062) Before, Gitea shows the database table stats on the `admin dashboard` page. It has some problems: * `count()` is quite heavy. If tables have many records, this blocks loading the admin page blocks for a long time Some users had even reported issues that they can't visit their admin page because this page causes blocking or `50x error (reverse proxy timeout)` * The `actions` stat is not useful. The table is simply too large. Does it really matter if it contains 1,000,000 rows or 9,999,999 rows? * The translation `admin.dashboard.statistic_info` is difficult to maintain. So, this PR uses a separate page to show the stats and removes the `actions` stat. ![image](https://github.com/go-gitea/gitea/assets/2114189/babf7c61-b93b-4a62-bfaa-22983636427e) ## :warning: BREAKING The `actions` Prometheus metrics collector has been removed for the reasons mentioned beforehand. Please do not rely on its output anymore. 2023-06-03 17:03:41 +03:00			`</h4>`
			`<div class="ui attached table segment">`
			`<table class="ui very basic striped table unstackable">`
			`{{range $statsKey := .StatsKeys}}`
			`<tr>`
			`<td width="200">{{$statsKey}}</td>`
			`<td>{{index $.StatsCounter $statsKey}}</td>`
			`</tr>`
			`{{end}}`
			`</table>`
			`</div>`
			`</div>`
			`{{template "admin/layout_footer" .}}`