Number of relevant and remedied computers for a fixlet

(imported topic written by jnmoore91)

How do I get the number of remedied computers for a fixlet?

I know how to get the number of relevant computers for a fixlet: ‘applicable computer count of bes fixlets whose (name of it is “C - Apple iTunes 8.1 Available - Windows XP/2003/Vista/2008”)’

However, I also want the number of remedied computers. I don’t see any obvious way to do this.

(imported comment written by BenKus)

There are two ways to do this:

  1. Look at all computers that have the Fixlet that used to be true and now is false (this will only work in web reports):

number of results whose (not relevant flag of it AND exists last became relevant of it) of bes fixlets whose (name of it = “C - Apple iTunes 8.1 Available - Windows XP/2003/Vista/2008”)

  1. Look at all the actions from a Fixlet with a “complete” status:

number of results whose (status of it = bes action status fixed) of bes actions whose (name of source fixlet of it = “C - Apple iTunes 8.1 Available - Windows XP/2003/Vista/2008”)

(imported comment written by jnmoore91)

Thanks, that did the trick.

Couple of questions:

  1. Do you know why this only works in web reports and not on the BES Console Presentation Tool?

  2. I examined bes fixlet result before, but it didn’t appear obvious that I could derive a solution using it’s properties. Is there a support document that explains these properties? The Inspector Libraries found on (http://support.bigfix.com/fixlet/) doesn’t seem to offer in depth analysis or examples.

  3. What does “last become relevant” mean?

(imported comment written by BenKus)

Answers:

  1. Yes… Fixlets keep a simple history of the last time it became relevant, the first time it became relevant, and the last time it became nonrelevant. So each Fixlet/computer pair stores a timestamp in the database… So if you have a large deployment of say 100,000 computers and you have something like 2000 Fixlets and to store the timestamps will end up being something like 20 bytes in the end, then you will have (20 bytes x 100,000 x 2000 = 4 GB) in the worst case scenario… And so to avoid the memory usage hit of loading this data or a portion of this data, the console doesn’t allow you to access this information.

  2. I prefer the inspector search: http://support.bigfix.com/inspectorsearch/inspector_search.html . Try typing “bes fixlet result” in the “Type”… It is still lean on examples, but at least you can search around fairly easily.

  3. It is the time the Fixlet was last relevant.

Ben

(imported comment written by jnmoore91)

Awesome Ben,

Thanks for the useful responses.

I have another relevance question. Say I have a relevance query that returns a collection of time intervals (plural time intervals). Is there a way to find the sum of these time intervals?

primitive example:

Q: (week; day; hour; minute)
A: 7 days
A: 1 day
A: 01:00:00
A: 00:01:00
I: plural time interval

I know if I do

week + day + hour + minute

it will find the sum, but I don’t know how to do the same thing over a collection of time intervals. Right now the work around I’m thinking of using is to use javascript to find the sum for me OR maybe concat the results of the first relevant results into the "

week + day + hour + minute

" form and plug it back into the relevance evaluator to get my results.

I’m leaning toward the javascript solution, but if you have another way to do it in relevance, that’d be great!

–Jerroyd

(imported comment written by jessewk)

Try this:

Q: (sum of (it / (1 * second)) of (week ; day ; hour ; minute)) * (1 * second)

A: 8 days, 01:01:00

T: 0.109 ms

I: singular time interval

Or depending on how you get the list:

Q: (week + day + hour + minute)

A: 8 days, 01:01:00

T: 0.074 ms

I: singular time interval

(imported comment written by jessewk)

Also, I should note that there is already a new feature implemented on our next major release branch which will allow you to just use ‘sum’ on time intervals. So you’ll be able to just use ‘sum of (week;day;hour;minute)’.

Jesse

(imported comment written by jnmoore91)

sweet. awesome. thanks for the info. can’t wait for version 8.0