Hi all
I have activated the “AIX OS level” analysis to retrieve the “AIX full OS Level” and everything works fine.
Now I would like to access this information from an external procedure. It’s possible to know where the analysys output is stored in the bigfix database ? (wich database and table)
p.s.
BigFix 9.5
tnx
While this data is technically available via the BigFix database, in general, we don’t recommend querying the database directly for a number of reasons including the potential for change associated with the database schema, as well as the potential for performance and functional impact to BigFix. Instead, I’d recommend leveraging the REST API for such use cases. You can perform a POST operation against /api/query and pass it something like the following session relevance parameter:
(name of computer of it, value of it) of results (bes property "AIX Full OS Level", bes computers)
If you did want to get at it from a SQL view, you would have to know the site, analysis, and property ID. then query one of the views. Depending on what products you have installed, there are different tables you would want to use (as some are easier than others).
To mimic what Aram said, API is preferred. But if you must have SQL queries, use the views instead of tables. That should give you a bit more stability.
Also realize that the SQL views will have deleted computer content, so you would have to add in additional logic to get only live results. Another reason why API is better.
I’m sure that api is the best way…but for our “self made” configuration database there is no other way (at the moment) that query directly the BigFix database.
I will appreciate if you can give me any suggestion to find the right table where this analysys results is stored. There is no problem about deleted computers, it’s ok to retreive also information about this (will be discarded after, in the cmdb)
I second the comments above stating that the rest api should be the preferred approach for retrieving data. However if you still want to proceed, check out the view dss.property_results or tables QUESTIONRESULTS\LONGQUESTIONRESULTS