We are trying to get this relevance to work on a automatic computer group and it is not pulling in cloud devices.
(if (exists setting "ILMT_SUA_public_cloud_name" whose (exists value of it) of client) then (exists key "xx:environment-type") whose (value of it as lowercase != "production") of tags else (it = "development" or it = "integration testing" or it = "quality assurance" or it = "pre-production" or it = "lab") of (value of setting "xxx_status" of client as string as lowercase)) AND (not exists true whose (if true then in proxy agent context else false))
The else statement for xxx_status is working. We submitted an idea for this scenario here, https://bigfix-ideas.hcltechsw.com/ideas/BFMCLOUD-I-35
Why is it not giving me tag data on cloud endpoints where the native agent is installed?
The reason is that the tags get retrieved by the Plugin server which then directs them to BFEnterprise but the native client is never purview of that data. It doesn’t have it, it can’t use it, as far as it is concerned… it doesn’t exist.
One thing that was released to deal with situations like this is “Server Based” groups - the idea is that those are not evaluated against clients (they are never send down anywhere), they reside and are updated purely on what information is in BFEnterprise, hence they cover the plugin portal data too. Do bear in mind that it is not “perfect” imho but I can share an example that I was able to get to work with Support (had to get them involved due to some inner quirkiness!):
- Created a global property with the following code - the last statement does need to be “undefined”, you put user-defined error or anything else in there and things then don’t work with the Server Based group well (afore-mentioned quirkiness!)
if (exists property "tag") then (if exists tags whose (key of it = "backupPolicy" and value of it != "None") then "TRUE" else "FALSE") else undefined
- Create a “Server Based” group to check one of the expected values - the “Provider” is a normal “client-based” global property
Why I say the approach is not perfect? Well, there are quirks to start with; Server-Based properties while a great concept to be really powerful need to have the ability to use ALL properties in DB which they currently don’t (always require, “global properties”, so for every single use case you’d need to create more and more global properties that really shouldn’t be global because their definition is not even designed to handle “all machines”.; etc… Anyway, hope it helps you with your use case and can get it to work.
1 Like
Thanks for the guidance.
around the area of "and value of it != “None”
Is the None something you expect from the tag or is that just a general does not exist thing?
Ah no, should’ve removed it! it was specific requirement in my use-case (they only wanted me to pick values if the tag had a valid value, so “None” was my way to filter once that were coming in with no value)…