EOC Not Accepting SQL Filter Queries for Custom Properties

Please use NodeCustomProperty.City = 'Atlanta' (without the dot between Node and CustomProperty) in those resources where Node.CustomProperty doesn't work.

We are aware of the fact, that the naming is not consistent across all resources and fix for this is in our plan for some future release.

Thank you very much. This solution does work on the custom Node properties. But it does not work on the custom Interface properties.

None of these queries work:

  Interface.CustomProperty.WAN = 'false'

  InterfaceCustomProperty.WAN = 'false'

  Interface.CustomProperty.WAN = '0'

  InterfaceCustomProperty.WAN = '0'

The first of these worked on our system before applying the SP1 update for EOC v1.3 (and in v1.2).

The exact syntax could differ for different resources, anyway if this is something which worked in EOC 1.3 and stopped working in SP1, please create a support case for this.

There was also an issue with using custom properties on Interfaces.

I support case was opened with SW. It turns out that is a bug (or several) in SP1 for EOC v1.3. I patch was supplied by tech support to correct this, but it a one-off patch for anyone having this issue.

With the patch the syntax turned out to be:

For Nodes: NodeCustumProperty.City  (no dot after node)

For Interfaces:  I.CustomProperty.WAN

Note: The syntax of the SQL filters are different on many of the resources in EOC. You can have 3 or 4 different syntax on a single view to get the same results in different resources.I think this very poor quality assurance and concern for the customer on SolarWinds' part. It is just plain rediculous.