That's actually quite useful indeed. I wonder if it would show the total of all displayed rows or all rows that exist in general?

I reckon it would be more useful for the displayed ones? So when you search eg for /blog/ you would get a summary of all shown /blog/ rows? Or maybe also the one that were not shown because maybe a limit of 10 is selected and there are 200 rows that much this pattern?

I could even imagine it would also work well to display it on the top but bottom is probably better

Hi, well, displayed data only, of course (range, website). I rarely use search, though (e.g. never), so that is less important, but if you like... I mostly use overall report. About display, does not really matter to me as long as we have the numbers crunched, below lead header, inside it, or at the bottom :)

Thanks!

maybe also the one that were not shown because maybe a limit of 10 is selected and there are 200 rows that much this pattern?

👍 Total row would apply to the whole current datatable (total would include the rows that could be paginated)

Note that there is such feature already implemented for the Database Usage tables: