Hi all,Β weβveΒ set up a few reports across different tenants, but honestly, running them manually every time is starting to get annoying π .Β Is there a better way to handle this across multipleΒ HexnodeΒ portals without logging into each oneΒ again and again?Β
How are you automating reports across multiple Hexnode tenants?Solved
Replies (10)
Yeah, that gets painfulΒ pretty quicklyΒ once the number of tenants grows. We ran into the same thing.Β What worked for us was switching toΒ scheduledΒ reports, but also slightly changing how we approached it. Instead of trying to pull everything from one place, we let each tenant handle its own reporting and just push the data out.Β
What helped in our case was leaning into how the platform is structured. Each tenant already has strong reporting capabilities, so we focused on configuring them individually in a consistent way. Once every tenant is set up with the same kind of report and schedule, the overall visibility comes together quite nicely at the MSP level.Β
Oh okay, soΒ itβsΒ not like a centralized dashboard kind of setup?Β
Not really. It works more like a push model.Β What we did was, for each tenant, we first built the exact custom report we needed, like outdated OS or inactive devices. Then we went intoΒ scheduledΒ the reports and set it up to send automatically on a fixed schedule. We usually go with daily or weekly depending on how often we want updates.Β
Got it.Β So,Β everything just lands in email? Doesnβt that get messy after a point?Β
ItΒ definitely canΒ if youΒ donβtΒ structure it properly. That part matters more than people expect.Β We send everything to a single central inbox, or you could even route it into a ticketing system if that fits your workflow better. Also make sure the format is CSV, not PDF, since the idea is toΒ actually useΒ the data later.Β
Another thing that really helped us was naming. If every report clearly includes theΒ tenantΒ name, it makes life much easier when you start dealing with multiple files.Β
YeahΒ that makes sense. But even then,Β youβllΒ still end up with a lot of CSV files piling up, right?Β
True, andΒ thatβsΒ where the last piece comes in, aggregation.Β Instead of opening each file one by one, we route all the attachments into a single folder, could be local or even SharePoint. Then in Excel, we use Power Query and choose the βGet Data from FolderβΒ option. It automatically reads all the CSV files in that folder and combines them into one dataset.Β
Since the reports all follow the same structure and naming, you can still clearly see which device belongs to which tenant after everything is merged. It ends up beingΒ pretty clean.Β
YeahΒ this soundsΒ way moreΒ manageable than whatΒ weβreΒ doing now. Thanks for explaining it so clearly! πΒ