HubSpot Reader runtime considerations

Metrics monitored by the HubSpot Reader

Metric	Description
Number of DDLs	Number of data definition language operations
Number of updates	Number of update operations
Number of inserts	Number of insert operations

For more information, see Monitoring Guide.

The HubSpot Reader does not currently capture DELETE operations.
The names of custom objects must end in __c.
Records for objects that do not support incremental load are synced at every polling interval, which can result in duplicate records. Enable Merge mode for the targets of objects that do not support incremental load to avoid duplicate records.
Objects whose time of last update cannot be determined by Striim are duplicated in the target at every polling interval. Typically this occurs when an object does not have a Last_Modified_Date field.
When a table has both an ID field and an Last_Modified_Date timestamp field, using the Last_Modified_Date timestamp field as the incremental load marker for incremental load operations is a best practice. Using the ID field as the incremental load marker can lead to data loss when an incremental load operation causes high-volume data ingestion. To correct this state, remove the incremental load marker for the affected table and perform a resync.
Due to HubSpot API filter limitations, do not use CreatedAt, UpdatedAt, or Archived for a check column. Valid fields are ID, lastmodifieddate, object_lastmodifieddate, and custom date fields. Hubspot native objects such as FORM do not have a lastmodifiedfield and needs to be full resynced.