wptbh (wptbh) asked a question.
I have a Okta restreader client which polls the Okta server every 300 seconds. I am seeing many duplicate logs getting pulled causing high disk space usage .
Is there any way to prevent getting duplicate events ?
Hello,
This is Adrian with Okta Support. Thank you for posting this inquiry in our community.
The Okta endpoint for Events will list the Events as they occur, without any duplicates. However, you are seeing same events in your reports due to the time-frame between the API calls. I imagine that your restreader client is pulling a limited amount of events every 300 seconds, based on some filters that you specified. The reason you are seeing duplicates is that the client is pulling the same events from the last batch because in the time-frame of 300 seconds there weren't sufficient events logged to override the last batch completely.
I hope I have provided sufficient insight.
Have a great day!
Adrian Lazar,
Tier 2 Support Engineer.
Hello,
Thanks for posting your inquiry in Okta Community Portal.
If you receive a great answer to your question(s), please help readers find it by marking it the best answer. Hover over the answer and click "Best Answer."
Thank you,
Mike Davie
Okta Help Center
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
May Okta Community Buzz
Stay ahead of the curve with Okta for AI Agents, new Okta Learning live sessions and labs, shout-outs, and top trending topics—all aimed at enriching your Okta journey.
Hello,
This is Adrian with Okta Support. Thank you for posting this inquiry in our community.
The Okta endpoint for Events will list the Events as they occur, without any duplicates. However, you are seeing same events in your reports due to the time-frame between the API calls. I imagine that your restreader client is pulling a limited amount of events every 300 seconds, based on some filters that you specified. The reason you are seeing duplicates is that the client is pulling the same events from the last batch because in the time-frame of 300 seconds there weren't sufficient events logged to override the last batch completely.
I hope I have provided sufficient insight.
Have a great day!
Adrian Lazar,
Tier 2 Support Engineer.