# Web service telemetry in Business Central
When telemetry is enabled, Business Central logs web service calls to partner telemetry. Telemetry enables you to monitor which endpoints are being used and the category of the web service, like SOAP, OData, or API. You can also see possible failures, which are tracked in the HTTP status codes for the calls.
## Incoming web service telemetry
Web services telemetry gathers data about SOAP, OData, and API requests through the service. It provides information like the request's endpoint, time to complete, the SQL statements run, and more.
When calling Business Central web services, you can inject information about the caller into telemetry for REST API and OData calls.
 Setting the HTTP header _UserAgent_ logs requests with the httpHeaders dimension.
 Setting the HTTP header _client-request-id_, logs requests with the httpHeaders dimension and it also sets the "OperationId"/ClientActivity in Application Insights.
This capability means you can use telemetry to see who's calling Business Central REST APIs and OData web services. It also lets you correlate to telemetry from other web services, if you use Azure Application Insights to instrument them.
See Analyzing Incoming Web Services Request Telemetry<../administration/telemetry-webservices-trace>.
## Web service access key telemetry
Business Central emits telemetry data about the success or failure of authenticating web service access keys on web service requests.
> IMPORTANT
> Starting October, 2022, the use of access keys (Basic Auth) for web service authentication is deprecated and not supported<../upgrade/deprecated-features-platform#accesskeys> in Business Central online. We recommend that you use OAuth2 instead. See Using OAuth to Authorize Business Central Web Services<authenticate-web-services-using-oauth>.
As a partner or customer, this data lets you monitor legacy web service access key use in on-premises environments and plan migration to OAuth authentication. Web service access keys aren't supported in Business Central online.
See Analyzing Web Service Access Key Telemetry<../administration/telemetry-webservices-access-key-trace>.
## Web service publish failure telemetry
If a web service couldn't be published or a published web service isn't working, most often it's due to an error in creating metadata for the web service. When telemetry is enabled, metadata creation failures are available in partner telemetry, along with a stack trace of the element responsible for breaking the web service metadata.
See Analyzing Web Service Publish Failure Telemetry<../administration/telemetry-webservices-publish-failure-trace>.
## Related information
Web Services Overview<web-services>
web-services-best-practices
Analyzing Incoming Web Services Request Telemetry<../administration/telemetry-webservices-trace>
Analyzing Web Service Access Key Telemetry<../administration/telemetry-webservices-access-key-trace>
Configuring Business Central Server<../administration/configure-server-instance>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/web-service-telemetry, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/webservices/web-service-telemetry/
