Click the Start a free trial link to start a 30-day SaaS trial of our product and join our community as a trial customer. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I'm pushing some data to AppDynamics using CURLs. I've noticed that when I don't explicitly send the eventTimestamp in the request, the business journey does not pick up the message. But I can found the message in the schema, and the eventTimestamp is equal, in these cases, to the pickupTimestamp.
Has anyone experienced this issue, or knows why this happens?
Solved! Go to Solution.
I reached out to Docs team about this Doc and this is what I heard back.
In the case of Business Journeys, the evenTimestamp field should be present or Business Journeys will not work. If you plan on using Custom Events while defining Business Journey, the custom events should send eventTimestamp field. If they don't, only the Business Journeys will not work.
Let me know if that helps.
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.