Dashboard Audit
Hello,
Has anyone been auditing on Dashboard usage.
We have a lot of dashboards and we want to know dashboard which weren't used for over 30 days.
I do not see an API for this, is there another to get this info.
Essentially we need find dashboard not being used for over 30 days then, we will mark them private for next 10 days and then remove them.
Thanks,
Ashish
Ashish Sikarwar
Posted 2 years ago路Last reply 2 years ago
10 comments
Ashish Sikarwar
OP2 years agoI think I got it! Thank you 馃榾
Ashish Sikarwar
OP2 years agoAre talking about scanning the logs for LM and look for specific dashboard URLs being used or not?
Ashish Sikarwar
OP2 years agoThank you for your response!
"Webserver Logs" where can I access that? Are you talking about our internal LM logs?
Mike Moniz
路2 years agoThe idea is that you add an HTML widget on all your dashboads that loads a webpage on a webserver to control/own. For example have the widget load https://www.asikarwar.com/LM-DashBoard-WindowsServersDashboard01 (if you had a website at asikarwar.com) then you can look for hits to "LM-DashBoard-WindowsServersDashboard01" in your server's website logs.
Basically this is a hacky workaround. There isn't anything built in you would have access to. You can submit feedback to LM as a feature improvement.
Ashish Sikarwar
OP2 years agoI see, will try this out. Thanks a lot Mike!
Ashish Sikarwar
OP2 years agoI may need a CORS enabled webpage to be loaded from LM.
LM User
路2 years agoTheoretically, you could have LM monitor those logs and parse through the usage numbers, which you could then put on a dashboard. This is becoming more interesting. I may have to look into doing this myself.
LM User
路2 years agoLM has a way of tracking that internally, but i don't know if a way within the product to tell since it's not logged to the audit log. Your CSM might be able to pull a report telling you which dashboards are accessed by which users.
You could use a third party counter (think 1992), but since most browsers block 3rd party cookies, it probably wouldn't be very accurate.
Mike Moniz
路2 years agoThe counter thing is a good idea. If you don't care about tracking users, a widget that loads a webpage you control might work. It would need to allow CORS and need to be careful about browser caching, but might just be as simple as checking the webserver logs to see if the url was accessed at all in the past X days.
LM User
路2 years agoThe webserver logs is the way to go. It's trivial for LMers to access that data (through Looker). Unfortunately it's not exposed to customers. It would be a good feature for LM to build in: tracking which are the most used features of LM by which users. Are users going to the alerts page? Which dashboards are they using/not using? Are they looking at maps? How many have UIv4 turned on? etc.