Alarm event listener not getting all events from server?

hi, i’m using the code as showed in the alarm event viewer example, registered to the NewAlarmEvent. (server and SDK DLL ver 2017).

We’ve noticed that quite after some random time not ALL events are coming to our component or events come in after delayed time (seconded or even minutes).

  1. Is there a reason alarms could not be sent? (we do not filter any alarm)

  2. could you explain more about the paramerter: EndpointType.Server (i don’t use it right now - could it improve something)?

  3. in our alarms the description is being filled with some amount of data coming from 3rd parties, is there some limit on that? recommendation? could it make the system slow (a lot of events with this alarm types…)?

Thanks.

Hi

  1. a. Could you please try the same in the Smart Client and say if you have the same issue there?

b. Could you please then also try the same with the latest SDK?

  1. Nope, this parameter is only for information, it cannot improve the situation.

  2. There is only a limitation for displaying the description in the Management Client (32767 chars max). But there is no limitation on the level of SDK or database. However, you are right that it can make the system slow, as every event bears the full description in itself, so if they are huge, it can be also a problem. But if the events are not just slow, but are completely lost, it sounds like an issue, so I suggest to try what’s described in #1.