[MXS-4182] Session load indicator. Created: 2022-06-30 Updated: 2023-03-08 Resolved: 2023-01-31 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 23.02.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Naresh Chandra | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-176 | ||||||||
| Description |
|
Was: MaxScale Global CPU Usage Indicator At some times it's very hard to know why MaxScale is consuming High CPU utilization and which part in particular is causing it. We need an indication as to where the CPU is going. Which query or session is causing more CPU would be good and alert in the GUI with Critical/Warning/Notice in the GUI and through auto mail alert would be a good and it will be very useful feature for us. |
| Comments |
| Comment by Johan Wikman [ 2023-01-30 ] |
|
In 23.02 the session object returned by the REST-API will contain an integer field io_activity that reports the number of epoll-events handled for the session, during the last 30 seconds. The number will be shown in a new I/O Activity row by maxctrl show sessions and in a new I/O Activity column by maxctrl list sessions. In MaxGUI there will similarly be a new I/O Activity column in the Current Sessions display. On the one hand, the value provides an indication of the absolute amount of load caused by one session, on the other hand, when compared to the values of all other sessions what its relative share of the load is. Note that as the value is an amalgamation of the I/O activity during the last 30 seconds, very short peaks are not visible and it takes a while after the fact for the activity to both increase and decrease. |
| Comment by Johan Wikman [ 2023-01-31 ] |
|
This now partly fulfills the original request. The I/O Activity provides an indication of the load caused by a session. If this is found informative and useful, please create another issue for alerts, if that is deemed necessary. |
| Comment by Naresh Chandra [ 2023-02-03 ] |
|
Hi Johan, Thanks for the update and created the below ticket for alerting. |