Skip to content

Commit 2464091

Browse files
Merge pull request #272395 from ecfan/patch-1
Fix metrics and traces for SAP NCo
2 parents 228c9b0 + 464250b commit 2464091

File tree

1 file changed

+17
-5
lines changed
  • articles/logic-apps/connectors

1 file changed

+17
-5
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: daviburg
77
ms.author: daviburg
88
ms.reviewer: estfan, azla
99
ms.topic: how-to
10-
ms.date: 02/10/2024
10+
ms.date: 04/18/2024
1111
---
1212

1313
# Connect to SAP from workflows in Azure Logic Apps
@@ -1082,9 +1082,9 @@ See the steps for [SAP logging for Consumption logic apps in multitenant workflo
10821082

10831083
---
10841084

1085-
## Enable SAP client library (NCo) logging and tracing (Built-in connector only)
1085+
## Enable SAP client library (NCo) logging and tracing (built-in connector only)
10861086

1087-
When you have to investigate any problems with this component, you can set up custom text file-based NCo tracing, which SAP or Microsoft support might request from you. *Traces* include text information that's used with metrics. This information is sent to the Application Insights table named **traces**. By default, traces are sent at 10-minute intervals. By default, this capability is disabled because enabling this trace might negatively affect performance and quickly consume the application host's storage space.
1087+
When you have to investigate any problems with this component, you can set up custom text file-based NCo tracing, which SAP or Microsoft support might request from you. By default, this capability is disabled because enabling this trace might negatively affect performance and quickly consume the application host's storage space.
10881088

10891089
You can control this tracing capability at the application level by adding the following settings:
10901090

@@ -1097,6 +1097,16 @@ You can control this tracing capability at the application level by adding the f
10971097
* **SAP_RFC_TRACE_DIRECTORY**: The directory where to store the NCo trace files, for example, **C:\home\LogFiles\NCo**.
10981098

10991099
* **SAP_RFC_TRACE_LEVEL**: The NCo trace level with **Level4** as the suggested value for typical verbose logging. SAP or Microsoft support might request that you set a [different trace level](#trace-levels).
1100+
1101+
> [!NOTE]
1102+
>
1103+
> For Standard logic app workflows that use runtime version 1.69.0 or later, you can enable
1104+
> logging for multiple trace levels by separating each trace level with a comma (**,**).
1105+
>
1106+
> To find your workflow's runtime version, follow these steps:
1107+
>
1108+
> 1. In the Azure portal, on your workflow menu, select **Overview**.
1109+
> 2. In the **Essentials** section, find the **Runtime Version** property.
11001110

11011111
* **SAP_CPIC_TRACE_LEVEL**: The Common Programming Interface for Communication (CPI-C) trace level with **Verbose** as the suggested value for typical verbose logging. SAP or Microsoft support might request that you set a [different trace level](#trace-levels).
11021112

@@ -1170,22 +1180,24 @@ With the August 2021 update for the on-premises data gateway, SAP connector oper
11701180

11711181
### Metrics and traces from SAP NCo client library
11721182

1173-
*Metrics* are numeric values that might or might not vary over a time period, based on the usage and availability of resources on the on-premises data gateway. You can use these metrics to better understand system health and to create alerts about the following activities:
1183+
SAP NCo-based metrics are numeric values that might or might not vary over a time period, based on the usage and availability of resources on the on-premises data gateway. You can use these metrics to better understand system health and to create alerts about the following activities:
11741184

11751185
* System health decline.
11761186
* Unusual events.
11771187
* Heavy system load.
11781188

11791189
This information is sent to the Application Insights table named **customMetrics**. By default, metrics are sent at 30-second intervals.
11801190

1191+
SAP NCo-based traces include text information that's used with metrics. This information is sent to the Application Insights table named **traces**. By default, traces are sent at 10-minute intervals.
1192+
11811193
SAP NCo metrics and traces are based on SAP NCo metrics, specifically the following NCo classes:
11821194

11831195
* RfcDestinationMonitor.
11841196
* RfcConnectionMonitor.
11851197
* RfcServerMonitor.
11861198
* RfcRepositoryMonitor.
11871199

1188-
For more information about the metrics that each class provides, review the [SAP NCo documentation (sign-in required)](https://support.sap.com/en/product/connectors/msnet.html#section_512604546).
1200+
For more information about the metrics that each class provides, see the [SAP NCo documentation (sign-in required)](https://support.sap.com/en/product/connectors/msnet.html#section_512604546).
11891201

11901202
### Set up SAP telemetry for Application Insights
11911203

0 commit comments

Comments
 (0)