9/16/2023 0 Comments Splunk okta![]() Provide the desired interval (60 seconds is recommended).Provide a unique and appropriate Name for the input (arbitrary value).With our Account defined we can now define and Input Enter the Okta Domain (NOTE: domain name only e.g.Provide a unique and appropriate Okta Account Name for the account (arbitrary value).Navigate to Configuration -> Okta Accounts.Using the Okta Domain and API Token from our Prerequisites section perform the following. Finally, the client will pause for the calculated pause time IF percentage of calculated available calls exceeds the defined Throttling Threshold Pctīefore we can define an input, we must provide account credentials.If the calculated number of expected calls exceeds the calculated remaining calls, the client will pause more aggressively.To decide how long the client should pause, it makes an assumption about the number of calls per second it and other clients are making (4 calls per second).if the response header says there are 100 calls available and the Warning Threshold Percentage is set to 75%, the remaining logic will act as if there are only 75 remaining calls If Avoid Rate Limit Warnings is enabled (please leave this enabled), the number of remaining calls evaluated from the response headers is reduced to the Warning Threshold Percentage of the actual remaining calls.If the response code is 200 (success), the client will evaluate the time left in the rate limit window along with the number of remaining calls available.If the response code is 429, we exceeded the rate limit the client will pause for the time left in the rate limit window + 7 seconds for a safety factor (67 seconds would be the max) Keep in mind that rate limits are shared among clients, and we cannot assume we are the only client.Īfter each API call is made, the response headers are evaluated to determine what the rate limit is, the number of remaining calls and the amount of time left in the rate limit window. Throttling Threshold Pct: below this percentage of available rate limits an adaptive throttling strategy is leveraged ![]() Tells add-on to use ONLY this percentage of API calls. Warning Threshold Percentage: Used to adjust rate limit avoidance target. There are 3 settings related to rate limits and the adaptive throttling / rate limit avoidance strategy the add-on uses.Īvoid Rate Limit Warnings: Enable throttling logic that attempts to avoid exceeding API throttling warning limits
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |