Related to:

Fetch a Dynamic Data, Gateway SQL, Dynamic target with a value as a rule target

Problem:

Dynamic target with a value as a rule target is something that can't be integrated.

Possible solution(s):

Given that having a dynamic target with a value as a rule target is something that can't be integrated.
We have replicated and created a workaround to achieve this.

Example Scenario:

1. The data (192.-.0.78) should be monitored even when the row has changed.
2. The data (192.-.0.78) should be present on either rows of the outbound column. Hence, giving us an ok severity if present and critical if not.
    

Here we have used this data as an example:

 
For us to segregate this values, we have configured the Gateway-SQL to obtain the data coming from both the columns:

Following this example should give you something like this. this way, the data should still be detected even if it's present on different rows.


 
Now, we will have a rule that should compare this two values, that when the data is not present on the second column, it should trigger a critical severity:


 
As an example, here we have removed the highlighted ip on the 2nd column:

 
This should then trigger a critical severity given that the data is not available on the 2nd column:

 
To also check to see if this can be detected even with a different row:


 

Related article(s):

https://support.itrsgroup.com/hc/en-us/articles/115004028369-Geneos-Gateway-SQL-Using-XPath-Sources

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.