Dear SAP Community,
within this blog I would like to describe the general setup of SAP Advanced Event Mesh Distributed Tracing. Another blog will follow soon how to configure and how to navigate within Datadog.
Distributed Tracing Motivation
In larger organizations applications consist of hundreds or thousands of services running across many hosts, and sharing messages over one or more event meshes.It is no longer possible to diagnose problems simply by troubleshooting an error message or looking at a log. You need a solution that can track an event all the way from the sending application, between event brokers, and to the receiving application.
Distributed tracing provides this ability, allowing an administrator to trace the lifecycle of an event as it travels through the event mesh.
All broker tiers in the Standard Plan will have Distributed Tracing included.
Configuration of Distributed Tracing in SAP AEM
What are the required configuration steps:
Enable the Tracing Destination
Go to User & AccountOpen the tab Distributed TracingClick Create Tracing Destination
Provide a meaningful name to that destination and select the type you would like to use.
Per Default ( with almost no additional configuration) it is AEM Insights.
If you would like to use another Open Telemetry Platform or another Datadog system please select the corresponding Destination Type. For this blog we use the Default setup
Click “Create”.
Configure the Message Broker
Access the Message Broker you would like to include into Distributed Tracing.
In the menu
Navigate to Messaging > Telemetry > SettingsEnable Trace and ReceiverSave the settings
In the same menu
navigate to Messaging > Telemetry > TraceFiltersClick on “create” Trace FiltersAdd the Topics which should be included:
In my case “>” for all topics was already available and I have addedI have added “sap.com/salesorder/create/>” to active the trace of SAP Sales OrdersOnce done you need to review, enable and save the new Filter
Now the message broker itself is configured and needs to be enabled.
Enable the Message Broker
Access the Message Broker you would like to include into Distributed Tracing.
In the menu
Navigate to Manage > Distributed TracingClick on “Enable”
The Message Broker will register itself top the underlying Tracing Destination. This setup can take some seconds.
Once enabled the system allows you to deploy the configuration from the step Configure the Message Broker (step before), therefore click on Deploy Configuration.
You will get a summary of the planned deployment and can confirm it, therefore click on Confirm and Deploy.
The Message Broker will register itself top the underlying Tracing Destination. This setup can take some seconds.
In case of no errors, you will get a confirmation that tracing has been configured.
Collector is running.Connection to the service is active.
Find more details links here:
https://help.pubsub.em.services.cloud.sap/Cloud/enable-dt-for-cloud.htm
Dear SAP Community,within this blog I would like to describe the general setup of SAP Advanced Event Mesh Distributed Tracing. Another blog will follow soon how to configure and how to navigate within Datadog. Distributed Tracing MotivationIn larger organizations applications consist of hundreds or thousands of services running across many hosts, and sharing messages over one or more event meshes.It is no longer possible to diagnose problems simply by troubleshooting an error message or looking at a log. You need a solution that can track an event all the way from the sending application, between event brokers, and to the receiving application.Distributed tracing provides this ability, allowing an administrator to trace the lifecycle of an event as it travels through the event mesh.All broker tiers in the Standard Plan will have Distributed Tracing included. Configuration of Distributed Tracing in SAP AEMWhat are the required configuration steps:Enable the Tracing DestinationGo to User & AccountOpen the tab Distributed TracingClick Create Tracing Destination Provide a meaningful name to that destination and select the type you would like to use. Per Default ( with almost no additional configuration) it is AEM Insights.If you would like to use another Open Telemetry Platform or another Datadog system please select the corresponding Destination Type. For this blog we use the Default setupClick “Create”. Configure the Message BrokerAccess the Message Broker you would like to include into Distributed Tracing.In the menuNavigate to Messaging > Telemetry > SettingsEnable Trace and ReceiverSave the settings In the same menunavigate to Messaging > Telemetry > TraceFiltersClick on “create” Trace FiltersAdd the Topics which should be included: In my case “>” for all topics was already available and I have addedI have added “sap.com/salesorder/create/>” to active the trace of SAP Sales OrdersOnce done you need to review, enable and save the new FilterNow the message broker itself is configured and needs to be enabled. Enable the Message BrokerAccess the Message Broker you would like to include into Distributed Tracing.In the menuNavigate to Manage > Distributed TracingClick on “Enable”The Message Broker will register itself top the underlying Tracing Destination. This setup can take some seconds.Once enabled the system allows you to deploy the configuration from the step Configure the Message Broker (step before), therefore click on Deploy Configuration. You will get a summary of the planned deployment and can confirm it, therefore click on Confirm and Deploy. The Message Broker will register itself top the underlying Tracing Destination. This setup can take some seconds.In case of no errors, you will get a confirmation that tracing has been configured.Collector is running.Connection to the service is active. Find more details links here:https://help.pubsub.em.services.cloud.sap/Features/Distributed-Tracing/Distributed-Tracing-Receiver.htmhttps://help.pubsub.em.services.cloud.sap/Cloud/enable-dt-for-cloud.htm Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
+ There are no comments
Add yours