collecting stats and displaying them, engine or in app

I’ve come to the point in my app where I want to collect all the information of my system and app and display it in cool graphs and stuff, I get that you can use collectD and statsD, but heres my question, what is the convention for when you have a “stats” part for your site, its not really part of the site, its not meant for the public so it feels messy sticking it in with the other business logic and views… so it would seam that an engine would be appropriate ? but I have other stats, stats that are specific to my app like user count, signup rate etc… is there a convention for how to do this ?

TLDR: is there a good convention for separation of stats pages and actual app

Jonathan Borg wrote in post #1064711:

TLDR: is there a good convention for separation of stats pages and
actual
app

http://newrelic.com/