CRM Integration Poller and Datadog

Created by David Sullivan, Modified on Mon, 9 Feb at 11:01 PM by Alsabana Sahubarali

INTERNAL USE ONLY

The contents of this page are for internal company use only. Do not distribute or share.

Objective

This article provides information on Datadog logs for the CRM integration poller.

Applies To

Datadog
CRM integration
Polling

Service Facets

Poller logs can mostly be found under the service facet, dsngpoller. However, dsngpoller calls providerconnection when making calls to the external CRM, so you may want to add providerconnection to your filter in case the error originates from there (often additional debug logs are emitted that you won’t see unless you include providerconnection).

Poller Datadog logs

Content	Description
DSNG Poller GetUpdated results	This log shows the number of records to be synced from CRM under the facet “@poll.count”. This includes records that have been detected but not synced by previous polls. This excludes records that do not meet polling conditions.
DSNG Poller Poll results	First batch of records synced during polling period. Only includes facet result_ids if Plugin Logs Debugging is enabled. The batch size is captured under “@poll.count”
DSNG Poller PollNext results	Subsequent batches of records synced per polling period. Only includes facet result_ids if Plugin Logs Debugging is enabled. The batch size is captured under “@poll.count”
DSNG Poller hit iteration limit for org	Indicates the maximum number of API calls have been used for the current polling period. No more polls can be made till the next polling period, including manual polls. At this time, the maximum number of API calls per polling period is 25.

DSNG Poller GetUpdated results example

DSNG Poller GetUpdated results.jpeg

DSNG Poller Poll results / DSNG Poller PollNext results example

DSNG Poller Poll results.jpeg

Datadog Queries

Query	When to use	Datadog views (remove index: main)
service:dsngpoller @or.org.guid:* @resource.type:* “DSNG Poller GetUpdated results” -@poll.item.poll_type:("UPDATE_BACKFILL")	To determine how many records need to be synced from CRM to Outreach. Facet “@poll.count” shows the number of records to be synced from CRM for the current polling period.	Count of records to be synced dashboard
service:dsngpoller @or.org.guid:INCLUDE_GUID @resource.type:INCLUDE_RESOURCE_TYPE ("DSNG Poller Poll results" OR "DSNG Poller PollNext results") -@poll.item.poll_type:("UPDATE_BACKFILL")	To determine how many records are being synced per API call or per polling period. Facet “@poll.count” shows the number of records synced per API call.	Count of records synced per API call
service:dsngpoller @or.org.guid:* @resource.type:* “DSNG Poller hit iteration limit for org” -@poll.item.poll_type:UPDATE_BACKFILL	Use to determine if the poller hit the iteration limit and had to stop. Check for “DSNG Poller hit iteration limit for org” during the time period records were not syncing.	Iteration limit reached dashboard
@poll.item.poll_type:UPDATE_BACKFILL @poll.item.table:Polls	Filter on Historic Data Loader polls
@poll.item.poll_type:UPDATE_BACKFILL @poll.item.table:AutoBackfill	Filter on Autobackfill polls. Autobackfill runs on a regular cadence to backsync records that the integration was unable to poll on a previous attempt due to Salesforce, for example delayed LDC
@poll.item.poll_type:UPDATE @poll.item.table:Polls	Filter on Update poller. Update poller is the regular polling that customers set the cadence for in the UI