--- title: Sync log message types description: Learn about the message types that PingDataSync writes to the sync log and how to include or exclude them in log publishers. component: pingdirectory version: 11.1 page_id: pingdirectory:pingdatasync_server_administration_guide:pd_sync_log_message_types canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdatasync_server_administration_guide/pd_sync_log_message_types.html llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: September 13, 2023 --- # Sync log message types PingDataSync logs certain types of log messages with the sync log. Message types can be included or excluded from the logger, or added to a custom log publisher. **Sync log message types** | Message type | Description | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | change-applied | Default summary message. Logged each time a change is applied successfully. | | change-detected | Default summary message. Logged each time a change is detected. | | change-failed-detailed | Default detail message. Logged when a change cannot be applied. It includes the reason for the failure and details about the change that can be used to manually repair the failure. | | dropped-op-type-not-synchronized | Default summary message. Logged when a change is dropped because the operation type (for example, ADD) is not synchronized for the matching Sync Class. | | dropped-out-of-scope | Default summary message. Logged when a change is dropped because it does not match any Sync Class. | | no-change-needed | Default summary message. Logged each time a change is dropped because the modified source entry is already synchronized with the destination entry. | | change-detected-detailed | Optional detail message. Logged each time a change is detected. It includes attribute values for added and modified entries. This information is useful for diagnosing problems, but it causes log files to grow faster, which impacts performance. | | entry-mapping-details | Optional detail message. Logged each time a source entry (attributes and distinguished name (DN) *(tooltip: \
\

A name uniquely identifying an object within the hierarchy of a directory tree.\

\
)*) are mapped to a destination entry. This information is useful for diagnosing problems, but it causes log files to grow faster, which impacts performance. | | change-applied-detailed | Optional detail message. Logged each time a change is applied. It includes attribute values for added and modified entries. This information is useful for diagnosing problems, but it causes log files to grow faster, which impacts performance. | | change-failed | Optional summary message. Logged when a change cannot be applied. It includes the reason for the failure but not enough information to manually repair the failure. | | intermediate-failure | Optional summary message. Logged each time an attempt to apply a change fails. Note that a subsequent retry of applying the change might succeed. |