This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:sidebar:remoteapi:apiref:reqformat:reqformat [22/07/2016 15:57] stan |
en:sidebar:remoteapi:apiref:reqformat:reqformat [25/05/2017 08:30] stan [Limitations] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| All actions are executed only through POST requests. Additional parameters (“params”) should be given in the form of JSON. Response is also returned as JSON. All text parameters, either sent or returned, are supposed to use UTF-8 encoding. | All actions are executed only through POST requests. Additional parameters (“params”) should be given in the form of JSON. Response is also returned as JSON. All text parameters, either sent or returned, are supposed to use UTF-8 encoding. | ||
| + | \\ :!: [[http://json.org|JSON]] is not supported HEX values, use DEC. | ||
| Request template: | Request template: | ||
| Line 21: | Line 22: | ||
| ===== Limitations ===== | ===== Limitations ===== | ||
| - | **Limits for logins and sessions:** | + | [[en:sidebar:remoteapi:apiref:limits:limits]] |
| - | + | ||
| - | * No more than 10 unsuccessful logins from one IP address per minute; | + | |
| - | * No more than 120 successful logins from one IP address per minute; | + | |
| - | * No more than 100 active sessions of one user from one IP address; | + | |
| - | * No more than 60 logins per minute. | + | |
| - | + | ||
| - | If these limits are met, IP address will be temporarily blocked. It can cause difficulty to log in to the system. | + | |
| - | + | ||
| - | **Limits for messages:** | + | |
| - | + | ||
| - | * No more than 10 million messages can be loaded by a user; | + | |
| - | * No more than 10 million messages can be loaded by a user within 2 minutes; | + | |
| - | * No more than 500 thousand messages can be imported per minute. | + | |
| - | + | ||
| - | If these limits are met, messages stop being loaded or imported. It may cause difficulties in executing reports, building tracks, etc. If this happens, you can clear the panels Tracks, Messages, and Reports (or simply reload the page) and try again. | + | |
| - | + | ||
| - | **Limits for reports:** | + | |
| - | + | ||
| - | * Online execution of a report takes up to 2 minutes; | + | |
| - | * Report execution on jobs takes up to 10 minutes; | + | |
| - | * Report execution on notifications takes up to 5 minutes. | + | |
| - | + | ||
| - | When the timeout is exceeded, report execution will be aborted. That means the report will not be generated. In this case, diminish time interval, number of analyzed objects, or scope of requested data (tables, charts, etc.). | + | |
| - | + | ||
| - | **Other limitations:** | + | |
| - | + | ||
| - | * No more than 3 heavy requests (e.g., message loading, report execution, etc.) can be processed simultaneously in a session; | + | |
| - | * No more than 10 API requests can be processed simultaneously during one session; | + | |
| - | * No more than 3 map tracings can be processed simultaneously during one session; | + | |
| - | * No more than 10 'avl_evts' requests can be processed during 10 seconds | + | |
|
