Alarms bug

[m.sabitov]

When i try get alarms from 2 system, with alert text filter, query has error, because variable "where" was change on first iteration, and on second iteration its variable incorrect.
aes.ctl 5200 line -changing variable, 5077 line - start iterations.
version: 3.14.5
In my project i use 2 language, if it important for you.

[leoknipp]

Hello,

I've checked the functionality of the AEScreen when using a filter for the alert text.
Everyting is working correctly.

If you define a filter text you have to use wildcards if the text is only a pattern. If no wildcards are defined you get only those alerts where the alert text matches.

E.g. the alert text is "Value to 1".
If the filter is defined as "*Value*" the alerts are listed in the result.
If the filter is defined as "Value" without wildcards the alerts are not part of the result.
If the filter is defined as "Value to 1" only those alerts are displayed where the alert text is exactly "Value to 1".

Best Regards
Leopold Knipp
Senior Support Specialist

[m.sabitov]

2 distributed system, 2 system select in filter, and text filter. You try this settings?

[leoknipp]

Hello,

yes, I tried these settings and it worked.
Do you get a log message when starting the query?
Are you maybe using a modified aes.ctl file (saved in the proiect directory)?

Best Regards
Leopold Knipp
Senior Support Specialist

[chris@blue-catalyst.co.uk]

I have found a similar problem with the alarm description.

I am working on a distributed system with 2x2 redundancy (v3.14 patch 10), selecting a description filter does not return any results when in closed mode, it does however return a result when in current mode.

The function dpGetAllDescriptions in the AES.ctl returns only a list of datapoints in the system that the UI is connected to - even if that system is not being queried! The function doesn't look at descriptions in the systems which should be queried.

I commented out dpGetAllDescriptions, and dynAppend after, within aes_asGetFromWhere which allowed the text filter to be applied to result of the alarm query to the Oracle database.

Note - the aes.ctl we have is a modified, so may provide a different result.

Best regards,

Chris

[leoknipp]

I have tested it and had a look at the AEScreen functions.
During the test I saw the same behaviour as you have seen during your test. The function dpGetAllDescriptions is not called for every system on its own.
I made an entry in our internal database and forwarded it to our developers.

Best Regards
Leopold Knipp
Senior Support Specialist