Hello
Running BigFix Inventory version 10.0.8 on Windows 2016 SQL installed locally. WE=e run a task every night to generate software and hardware reports that leverage the BFI Inventory api. These reports run during non peak hours and do not run when the import takes place.
Some days we see the information in the files are truncated. The file size in quite different as well. For example the software report is typically around 3.1 GB when we have this problem the file size is about 1.7 GB in size. Because of the truncation issue the information within the report is not usable. Other symptoms we see a vast difference in the total rows value and we see missing ]} formating at the end of the report.
The TEMA log doesn’t have any useful information. Is there another log we should be looking at, or is there debug logging we could enable that would track report creation?
There are a ton of logs all under the same location and there is debug level you can enable but reading through them is problematic. My suggestion is open a support case and let them do that for you. Couple of suggestions - see if you can map out the occurrences of the issues:
- Is there any pattern with regards to when they occur? (same days/times of day)
- Have a look if they don’t for example conflict with SQL maitenance/backup/reindexing/etc job? Any of those may impact (interrupt, even “break” the import itself")
- What is the situation with the BigFix Root server and BFEnterprise database? The BFI import on top of importing the raw scan files does import data directly from the BFEnterprise database, so same kind of thinking - any jobs/OS/etc outage on the platform server may be causing incomplete/partial import into BFI.
Is the BFI API query run from an external task? Also is the API query run using Limit and Offset options to step through the data? If it is run with offset and limit, multiple API calls will be logged to the tema.log.
The log can be reviewed to track how many times the API query is run and till what count.
1 Like