I’m trying to create a report that will show users all data that is collected from their machines. This is to alleviate transparency and trust issues in academia.
I’m thinking there are two ways to do this:
Create a report that an admin can run.
Create a Technician.html dashboard.
I have tried #1, but keep crashing the web interface once I start adding a bunch of properties/columns.
I have yet to try #2, but I’m not even sure that it’s possible.
Are you interested in telling them about the Actions & changes that have been deployed to their machine (“Action History”), or do you want to show them the results of Analysis properties that are being retrieved from their machine?
There’s an Action History database on the client that can be queried with SQLite (I don’t recall where it is though). For Analysis results, I did a little digging and it looks like they’re stored in plain text in each operator site.
Could you just use session relevance to dump all the properties of a computer and their values?
I’ll test this when i get home, but something like this:
(Display name of it, value of result of it) of elements of Reported property set of bes computer
You can use table rows and you can probably group it by the analysis it’s a part of to get a result that’s kind of like the bes console computer detail view
I’ve never used session relevance, is there a good guide for it?
I think that is exactly what I’m looking for, some client dashboard that the user clicks on and goes “ah, that’s what they are pulling form this system”… of course it would be way too much information, but it would appease the paranoid.
It seams to pick up globally activated properties and values, but not the locally activated ones… damn.It actually does the locally activated ones as long as the result is not an error/null
Is it possible to include session relevance inside of a client dashboard so that I can have a user click on the BigFix icon and click a “All information collected about my computer” tab? Or is session relevance not usable there?
I’m still looking on a primer for creating client dashboards, if you find a good link I’m happy to RTFM, but my search skills have led me in circles.
The challenge with the ClientUI is you do not have access to session relevance as session relevance only works on the root server.
I’m also pretty sure that the Client UI also cannot access Analysis or Fixlet results like you can in Session Relevance. As such – you’re essentially stuck recreating each relevance statement that you want to show in the Client UI. The big problem is that the Client UI doesn’t appear for the user until it has crunched all the embedded relevance. If you’re using expensive relevance it could be ~30 seconds before the ClientUI appears after login and then the data is cached until the user refreshes the dashboard.
( name of parent folder of it, (following text of first "Fixlet " of it | it) of preceding texts of lasts ".fxf" of name of it, ( (following texts of firsts "X-Property-ID: " of it) of next lines of it, (following texts of firsts "Subject: " of it) of it, (it;next lines of it) whose(it != "" AND it does not start with "--F5A") of next lines of next lines of next lines of it) of next lines of lines containing "Content-Type: application/x-bigfix-itclient-property" of it) of files whose( name of it ends with ".fxf" AND (name of it starts with "Fixlet " OR name of it contains "nalys") AND name of it does not start with "Subscription" AND exists lines containing "Content-Type: application/x-bigfix-itclient-property" of it) of folders of data folders of clients
I haven’t tried making a ClientUI dashboard as of yet, but I wonder if it allows for javascript to evaluate relevance async instead of using <?Relevance ?> style.
files "TriggerClientUI.exe" of folders "AppData\Local\Temp\BES\ClientUI" of folders of folders "C:\Users"
If you want to make everything a bit more optimal, you can only look at Analyses.fxf and Questions.fxf in every action site as those contain all the content that returns actual data values. Every other .fxf file only returns relevant or not.