BigFix Explorer and ServiceNow data adapter

1

Hi, we’re using BigFix Explorer and working all fine. I’m trying to update one of my queries to also include data collected from our ServiceNow Adapter, but it returns “nothing found”.

When I check WebReports I can see that particular property populated with valid data

when I try to use session relevance against our WebReports instance it returns also valid data

Simple session relevance query which returns data against our WebReport instance.

(name of it, last report time of it, value of results from (BES Property "SNOW_Owned_by") of it | "not found" ) of bes computer whose (name of it = "ComputerName")

I’ve tried to query other properties collected by our ServiceNow data adapter but no luck either

I will also open case with HCL Support but wanted to check if somebody has seen this issue already and might have a solution for this.

Thx!

2

So do I understand correctly that all of your queries work with Web Reports, but then when you switch to Explorer it fails, using the same relevance?

Does your 'simple case' that works with Web Reports, also work with BigFix Explorer?

And, are you using the REST API to query ( https://rootserver.local:52311/api/query ), so that it is forwarded to Explorer, or are you sending your query to Explorer directly?

3

Hi Jason, I’m sending query directly to my BigFix Explorer instance. We run into some issues with WebReports queries causing our WebReport instance to not respond and needed to be restared (Windows Service), therefore we’re directing our developers to use BigFix Explorer.
commandline I’m using is below (curl based)
curl -k -X POST --data-binary @D:\DATA\BFExplorer\BFRestQryTest2.txt --user "":"" https://bfexplorerFQDN:9383/api/relevance -o D:\DATA\BFExplorer\Output\BFRestQryTest2.json

Same can also be done through Python/PowerShell but using Curl now for testing purpose. The query works (not getting error message) but it does not return any data for these SNOW_xxx properties
Here is the query I’m using
{
"relevance": "(id of it as string | "not found", name of it as string | "not found", value of results from (BES Property "OS") of it | "not found", value of results from (BES Property "SNOW_Owned_by") of it | "not found", value of results from (BES Property "SNOW_Market") of it | "not found") of bes computers whose (name of it = "ComputerName1")",
"keys": "{id computer_name operating_system snow_owned_by snow_market}"
}

Output of the query
{
"result": [
{
"id": "1085695846",
"computer_name": "ComputerName1",
"operating_system": "Win11 10.0.26200.8893 (25H2)",
"snow_owned_by": "not found",
"snow_market": "not found"
}
],
"count": 1,
"plural": true,
"type": "( string, string, string, string, string )",
"evaltime_ms": 147.164
}

4

Jason, just heads up, I’m able to retrieve the servicenow data using “master operator” api account, which works for my solution as workaround, working with support to see if we can get this configured so that it can work with regular readonly api account also.

Just wanted to let you know. Rgds!

5

Final update on this one, it turned out that the role my API Account was assigned to did not have permissions to read the properties created/populated by the ServiceNow data adapter. Once I’ve updated this I’m now able to query correctly this info.

Issue with my regular session relevance where everything was working fine, was because I’ve used the MO account already. If I used same accounts then I would have seen problem right away, call it Monday blues and coming back from 2-week vacation.

1 Like