Skip to main content

Stripe Reader runtime considerations

Metrics monitored by the Stripe Reader

Metric

Description

Number of DDLs

Number of data definition language operations

Number of inserts

Number of insert operations

For more information, see Monitoring Guide.

Stripe Reader limitations

  • The Stripe Reader cannot populate data for the following columns because this data can only be retrieved by expanding the API response using the expand[] query parameter.

    • Coupons

    • Customers

    • PaymentIntent

    • PaymentLinks

    • Plans

    • Prices

    • Quotes

  • The Customers and Invoices tables do not capture updates unless these tables are fully resynced at each polling interval. Leave the Incremental Load Marker property empty to cause full resyncs for these or any other tables.

  • When a table has both an ID field and a Created timestamp field, using the Created 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.

Note

When you authenticate using OAuth, you grant Striim read permissions to your Stripe account. Because they require a higher level of permissions, the Stripe Reader can't read the following tables when you choose to authenticate using OAuth.

  • Accounts

  • BankAccounts

  • BalanceChangeFromActivitySummaryReport

  • BalanceSummaryReport

  • EndingBalanceReconciliationSummaryReport

  • ItemizedBalanceChangeFromActivityReport

  • ItemizedEndingBalanceReconciliationReport

  • ItemizedPayoutReconciliationReport

  • ItemizedPayoutsReport

  • ItemizedReconciliationForASinglePayoutReport

  • PayoutsReconciliationSummaryForASinglePayoutReport

  • PayoutsReconciliationSummaryReport

  • PayoutsSummaryReport

  • Reports

  • ValueLists

  • ValueListItems