Status monitoring
Status monitoring
Starting from versions Itgrix bx 3.6.0 and Itgrix Kommo 2.13.0, an API method for checking the application status at <Asterisk IP>:8077/status
is added. Periodic checks of the response to this request can be used to track the application status and automatically react to problems.
Examples of requests
The following are request examples for specific status elements with explanations of their intended use. The elements can be extracted from the response using the jq
utility, a json data processor available for installation on Itgrix-compatible systems, or simply by specifying the target element in the path
request parameter.
Full status data can be obtained by querying:
Here <Asterisk IP>
- is the address of the Asterisk server where the module was installed.
-s
- reduces the amount of intermediate output from curl
.
--digest -u
- specifies the method of authorization.
<login>
and <password>
- login and password for the admin panel.
The reaction that should follow upon identifying faulty states of the application is not described here and should be determined according to the user's needs.
Example of a response:
Stop/restart status of the application
Using the queries described below, you can track when and why an application stops working.
Possible values of app_state
:
Normal operation will return a value of
""
.The value
"stopped"
is returned when the application has encountered an error preventing further operation and is waiting for user action.The value
"restarting"
is returned while the application is restarting. This can be caused by a problem that is supposed to be resolvable by reconnecting and/or by a short pause, e.g. network problems. It can also be caused by a normal restart, e.g. when changing connection settings.
app_status
contains the overall status of the application, which can be "Ok"
/"Warning"
/"Error"
. This is the status that is displayed at the top of the main page in admin panel. Most often it corresponds to the running/restarted/stopped status, but in some situations it can provide additional information. For example, it can help in distinguishing between a normal restart and a restart due to an error.
app_err
contains error details, based on which the error text is generated under the application status on the main page in admin panel. This element can be useful in finding out the causes of the failure.
License change
This query helps to identify if the application has switched to a license with limited functionality. This can occur not only when the license expires but also due to connection issues with the licensing server.
license.type
returns the license type displayed at the top of the main admin page.
Possible values:
"Professional"
- paid license with full functionality."Subscription"
- subscription license with limited functionality."Free"
- free license with basic functionality.
license.valid_till
contains the license expiration date (the last day on which the license is valid
) in YYYYY-MM-DD
format.
Last updated