This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

target.sent.start.timestamp is not getting populated in Postclientflow when backend timeout happens

Posted on 06-06-2016 04:02 PM
remeeshnair
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

We have a Message Logging policy which is logging in target.sent.start.timestamp in PostClientFlow, but it look like whenever io timeout happens with backend this variable is not populating, because of this we are not able to calculate request processing latency for those timeed out requests. Did someone faced same situation?

I am using OPDK v4.15.07.03

Regards,

Remeesh.

0 4 280
Topic Labels
0 Likes
4 REPLIES 4

Posted on --/--/---- --:-- AM
remeeshnair
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

Can someone from apigee please help here?

0 Likes

Posted on --/--/---- --:-- AM
Not applicable
Reply posted on --/--/---- --:-- AM

Hi @Remeesh,

Sorry for the delayed response. The "target.sent.start.timestamp" being null when there are timeouts (both io and connect timeouts) was a known issue and is fixed as part of 15.07.03. Can you raise a support ticket for us to work with you on this one? Thanks.

Regards,

Rampradeep.

0 Likes

Posted on --/--/---- --:-- AM
Not applicable
In response to
Reply posted on --/--/---- --:-- AM

We are using OPDK 4.16.05.02. But still we are seeing the same issue. Can you please let us know if this has been fixed or we need to open an incident with Apigee ?

0 Likes

Posted on --/--/---- --:-- AM
remeeshnair
Bronze 1
Bronze 1
Reply posted on --/--/---- --:-- AM

Hi @Rampradeep Krishnamurthy

Thank you very much for the direction. I will raise an incident get this checked.

Regards,

Remeesh

0 Likes