Fixlet Debugger / QnA: Executes Client Relevance (which is what would be used to create Fixlet & Task Relevance (and Relevance Substitutions in ActionScript), and to create Analysis Properties. Itâs used to query the state of things on the client.
The Fixlet Debugger works like a âcopyâ of the BigFix Client. It can query pure-OS things like file paths and contents, Registry, RPM database, etc. just like the normal BigFix client.
But because itâs a copy of the BigFix client, there are some things that it canât tell because it doesnât have the context of the real client. It doesnât know things like âregistration address of serverâ, because thatâs only known within the real clientâs context. Also, itâs not constrained by things like CPU throttling that is enforced on the real client.
For Windows-only, the Fixlet Debugger has an option to switch from âLocal Fixlet Debugger Evaluatorâ mode to âLocal Client Evaluatorâ mode (on the Debugger-> Evaluate Using" menu item). In âClient Evaluatorâ mode, it actually passes the query to the real BigFix client, so that it can access client-only properties like âregistration address of serverâ. However in this mode it also is limited to the real clientâs CPU use, and must âwait its turnâ in the clientâs evaluation cycle before it can get a result.
(An interesting note is that you can run the Fixlet Debugger without even having the BigFix client installed. Iâm posting this from home, where I can try things out in the Debugger though I donât have BigFix here. You can download the Fixlet Debugger separately from the BES Client on the Utilities download page.)
Session Relevance is a query thatâs evaluated by the BigFix Server, not by the individual clients. This is what you are executing in the BigFix Console Session Debugger or in BigFix Web Reports. The language constructs and syntax are the same as Client Relevance, but there are different Inspectors that can be queried. Many of these Session Relevance-only inspectors have names starting with âbesâ, such as âbes computersâ, âbes sitesâ, âbes fixletsâ, etc.
Session Relevance is useful in some of the more advanced customizations like creating Custom Dashboards, Custom Web Reports, and REST API for importing/exporting data or performing other integrations / automations. Hopefully you wonât need to do much Session Relevance until you have a chance to get a firm grasp on Client Relevance, as trying to learn both at the same time would be confusing.