Skip to content

feat(okta): add rate_limit_early_limit configuration - #15835

Merged
andrewkroh merged 1 commit into
elastic:mainfrom
andrewkroh:okta/feat/rate_limit-early_limit
Nov 6, 2025
Merged

feat(okta): add rate_limit_early_limit configuration#15835
andrewkroh merged 1 commit into
elastic:mainfrom
andrewkroh:okta/feat/rate_limit-early_limit

Conversation

@andrewkroh

@andrewkroh andrewkroh commented Oct 31, 2025

Copy link
Copy Markdown
Contributor

Proposed commit message

Add support for the rate_limit_early_limit parameter to enable starting
rate-limiting before reaching the API response limit.  Values less than
1 are treated as a percentage of the limit, while values greater than or
equal to 1 are treated as the target remaining value.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

Add support for the rate_limit_early_limit parameter to enable starting
rate-limiting before reaching the API response limit.  Values less than
1 are treated as a percentage of the limit, while values greater than or
equal to 1 are treated as the target remaining value.

This can avoid causing alerts to Okta admins under bursts of system log
activity by having the integration stop making requests as it gets close
to the limit.
@andrewkroh
andrewkroh force-pushed the okta/feat/rate_limit-early_limit branch from 2727da8 to 5a927fb Compare October 31, 2025 20:53
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

@andrewkroh
andrewkroh marked this pull request as ready for review October 31, 2025 22:29
@andrewkroh
andrewkroh requested a review from a team as a code owner October 31, 2025 22:29
@andrewkroh andrewkroh added Integration:okta Okta Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Oct 31, 2025
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@andrewkroh andrewkroh added the enhancement New feature or request label Oct 31, 2025
@andrewkroh
andrewkroh merged commit d64faaa into elastic:main Nov 6, 2025
7 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package okta - 3.11.0 containing this change is available at https://epr.elastic.co/package/okta/3.11.0/

tehbooom pushed a commit to tehbooom/integrations that referenced this pull request Nov 19, 2025
Add support for the rate_limit_early_limit parameter to enable starting
rate-limiting before reaching the API response limit.  Values less than
1 are treated as a percentage of the limit, while values greater than or
equal to 1 are treated as the target remaining value.

This can avoid causing alerts to Okta admins under bursts of system log
activity by having the integration stop making requests as it gets close
to the limit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:okta Okta Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

3 participants