Sudden latency between Analytics Triggers and Journal

Avatar

Avatar
Validate 1
Level 1
jgrubbs
Level 1

Likes

0 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
jgrubbs
Level 1

Likes

0 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
jgrubbs
Level 1

15-07-2021

Hello all,

 

We've been relying on Analytics Triggers and the Journaling API in Adobe IO to collect important data. It has been going extremely well for over a month, providing us with a valuable bit of data in something close to real time.

 

However over the last day or two, the Journal endpoint continues to respond with "204 No Content". I can see that the Trigger events are still being generated according to the Triggers UI (in "Activation"), but the Journal doesn't seem to be getting them, or it isn't allowing me to pull them

 

I'm using the appropriate endpoint URL and path specified by the "Next" attribute. Even if I request "latest=true", I get nothing, and again the "Next" attribute points to the same URL and "since" parameter...

 

Is there some kind of traffic jam going on? I have a ticket open this morning with Client Care, but I fear the rep I'm interacting with doesn't have a grasp of what I'm describing. Despite my detailed explanation, with URLs and all, they're asking for "screenshots" and a step-by-step explanation. I'm not sure how to snap a photo of a data pipeline 🙂

 

I guess my question is: Is anyone else noting the same kind of latency? Is there some kind of back-end trouble at Adobe that needs to be fixed?

 

Thank you all

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Affirm 3
Employee
shikhartanwar
Employee

Likes

0 likes

Total Posts

13 posts

Correct reply

4 solutions
Top badges earned
Affirm 3
Affirm 1
View profile

Avatar
Affirm 3
Employee
shikhartanwar
Employee

Likes

0 likes

Total Posts

13 posts

Correct reply

4 solutions
Top badges earned
Affirm 3
Affirm 1
View profile
shikhartanwar
Employee

15-07-2021

There is definitely no latency at our side for the Journaling API, but to be doubly sure, could you help us with the IMS organization id and the journaling endpoint for debugging? I can go through our Splunk logs and verify if things are working correctly.

Answers (0)