Add service does not trigger analytics event anymore

MIP
1

Hi, I wrote recently about a service deprecation that triggers en exception.
I was using the AddEvent service which is now deprecated. I change my code and now use the Add service.

I know there is a slight difference of behavior but it seems to do the trick.
However we recently discover that alarms sent via Add service does not trigger analytics events created by our software.
For all I know the triggering part worked until I changed the service called.

It is possible that calling Add instead of AddEvent broke the analytics events triggers?
Is there a workaround?

Thx

2

Basically there are two ways that you make an Alarm:

  1. You send an Alarm, it is immediately visible in the clients.
  2. You send an Event, it is matched against the Alarm Definitions and if it matches an Alarm is triggered.

Using AddEvent you were sending an event (2). Using Add you are sending an alarm (1).

Yes, in my understanding this will break the functionality, no Analytics Event will be triggered and no matching against Alarm Definitions when you submit an Alarm.

As I see it possible workarounds are to use the deprecated AddEvent or to use the new Rest API instead.

3

I’ll try to use AddEvent but the data structure lacks many information :confused:

And for now, I do not have time to redevelop the full client using Rest API. But it clearly is top priority …

4

I do not know if this is any better. Another alternative is to use the MIP SDK. If of interest please see the Analytics Event Trigger via library sample. Sample documentation. Sample code.