I’m trying to use the SOAP API to retrieve the names and relevancy dates of fixlets for a group of computers (which will eventually be all computers, so I want this to be as efficient as possible). Here’s the session relevance statement I’ve got now (trimmed a little for clarity):
(name of computers of it, name of fixlets of it, first became relevants of it) of results (((bes computers) whose (name of it as lowercase starts with "abc")), (relevant fixlets of ((bes computers) whose (name of it as lowercase starts with "abc"))) whose (source severity of it = "Critical"))
The first issue is that I get multiples of most lines which, if I’m seeing the pattern, will only get worse once I remove the “whose” for bes computers. What I get is each relevant fixlet’s details once for each computer for which it’s relevant. If three computers are relevant, I’ll get each computers name, the fixlet name, and the specific computer’s relevancy date three times. If four, then four times each. When there’s hundreds (or thousands), it’ll be disastrous.
If I run the above session relevance for a specific bes computer (by ID), I get exactly what I’d expect…that one computer’s data once. So, I could run thousands of individual API calls, one for each computer, but that sounds like it could be disastrous as well.
Does anyone have any insight before I bring down our server?