PingOne Extension - Suggessions

observefdfx — Fri, 19 Jun 2026 15:03:17 GMT

We have a use case of ingesting PingOne logs and created workflow and ingesting via direct API call to PingOne. Ingesion is going good but to avoid duplicates, scanning the logs for dups which is causing additional cost for scanning. We thought of PingOne Extension may solve the issue but seems extension will not handle. Looking for suggessions on this.

Re: PingOne Extension - Suggessions

sujit_k_singh — Tue, 23 Jun 2026 00:49:38 GMT

Hi @observefdfx

The PingOne Extension won't help here — it's designed for metrics, not log dedup logic.

The real fix is preventing duplicates at source (cursor tracking), not detecting them post-ingest.
Honesty. I never faced this issue but i would suggest to look at this from the ingestion side rather than scanning after the fact.
PingOne Activity API supports an after cursor for pagination. Store the last processed event ID or timestamp between workflow runs and only pull events after that point. This eliminates overlapping time windows and removes the need for dedup scanning entirely.

Thanks,

Sujit

topic Re: PingOne Extension - Suggessions in Extensions

PingOne Extension - Suggessions

Re: PingOne Extension - Suggessions