When Sosivio finds an application not configured properly, it will send an action to adjust the request and limits configured to the command center. Each application with a recommendation will be displayed in a table with the most prioritized container first:
- Application name - the namespace of the application with the application name
- Resource Status - States weather the application is over-allocated, under-allocated, has no limits set, or is properly profiled.
- What Happend - Information about what will happen if recomendations are not implemented
Clicking on the details button will open a table with details for the recommended allocation. The table under each application recommendation displays the following for CPU and Memory request and limits:
- Over/Under/No limit/OK - States weather the container is over-allocated, under-allocated, has no limits set, or is properly profiled.
- What will happen - Information about what will happen if recomendations are not implemented
By clicking on the container button, users can switch between the different containers in the Pod.
When clicking on the Recommended Allocation button, a pop up will appear with the current and recommended values for each container. The most prioritized container appears at the start - base on Sosivio's priority calculation. The pop up window displays values for the current and recommended values for CPU Request, CPU Limit, Memory request, and Memory Limit. The container average and max value of CPU and Memory are diplayed at the bottom of the pop up window.
When the recommendation is applied, the profiling data is reset and users will have to wait at least 10 minutes for enough data to be collected before any further recommendations for that same application can populate.