(imported topic written by boostaz191)
number of relevant fixlets whose (source severity of it as lowercase = “critical”) of sites
I am trying to find my worst offenders for patching requirments.
(imported comment written by jessewk)
Computers per critical Fixlet:
(name of it, number of applicable computers of it) of bes fixlets whose (source severity of it as lowercase contains “critical” AND exists applicable computer of it)
Critical Fixlets per computer:
(name of it, number of relevant fixlets whose (source severity of it as lowercase contains “critical” of it) of it) of bes computers
(imported comment written by boostaz191)
JessewK thanks for your help. However my results are not returning anything of value… Here is my analysis:
Critical Fixlets
Period Every Report
(
name of it, number of relevant fixlets
whose
(
source severity of it as lowercase contains “critical” of it
)
of it
)
of bes computers
(name of it, number of relevant fixlets whose (source severity of it as lowercase contains “critical” of it) of it) of bes computers
Important Fixlets
Period Every Report
(
name of it, number of relevant fixlets
whose
(
source severity of it as lowercase contains “important” of it
)
of it
)
of bes computers
(name of it, number of relevant fixlets whose (source severity of it as lowercase contains “important” of it) of it) of bes computers
Moderate Fixlets
Period Every Report
(
name of it, number of relevant fixlets
whose
(
source severity of it as lowercase contains “moderate” of it
)
of it
)
of bes computers
(name of it, number of relevant fixlets whose (source severity of it as lowercase contains “moderate” of it) of it) of bes computers
low Fixlets
Period Every Report
(
name of it, number of relevant fixlets
whose
(
source severity of it as lowercase contains “low” of it
)
of it
)
of bes computers
(name of it, number of relevant fixlets whose (source severity of it as lowercase contains “low” of it) of it) of bes computers
Site Specific Fixlets
Period Every Report
(
name of it, number of relevant fixlets
whose
(
source severity of it as lowercase contains “site specific” of it
)
of it
)
of bes computers
(name of it, number of relevant fixlets whose (source severity of it as lowercase contains “site specific” of it) of it) of bes computers
Here are My Results:
PC ID Critical important Moderate Low SiteSpecific
PC1
PC2
PC3
PC4
PC5
PC6
(imported comment written by jessewk)
Hi boostaz,
The relevance I gave you is session relevance and will not work when evaluated by clients. It is intended for evaluation in a wizard/dashboard/custom report.
If you want clients to report these values as part of a retrieved property, you need to use different syntax. Try this:
number of relevant fixlets whose (value of header “x-fixlet-source-severity” of it as lowercase contains “critical”) of sites
Please note that this is an expensive operation for the client to evaluate and I recommend that you do not set these properties to evaluate on every report. I would suggest once an hour or so.
(imported comment written by sthull)
Hi boostaz1,
It’s definitely a good idea to gather this info using session relevance in Web Reports since the information has already been reported by the clients. It is a bit redundant to have the clients evaluate it again as part of a retrieved property.
You could also use relevance like the following, which has the side benefit of being ordered by computer name:
(it as string, multiplicity of it) of unique values of names of applicable computers of bes fixlets whose (source severity of it as lowercase = “critical”)
Regards,
Steve