Troubleshooting What-if Simulation issues
Issue symptom
The GUI displays warnings related to missing data or incomplete simulation.
Resolution
Use the following information to identify and resolve issues:
Message | Explanation | Solution |
---|---|---|
Warning! Data is missing: The simulation may not be complete. | From the selected deployments, one or more deployments are not included in the simulation. This message appears at the top of the Simulation page. | Click Learn more to view the errors associated with each deployment. It could be one of the errors listed in the rows below. The warning message displays the name of the deployment that helps you identify the deployment which is resulting in an error. |
Access denied. | You do not have the permission to access the requested entity. The following permissions are required to access a What-if Simulation:
| Contact your administrator to request for access. For details, see Configuring-authorization-profiles. |
Missing number of pods. | Data about the number of pods that are running in a deployment is mandatory to generate a simulation. When this data is not available for the last 7 days, the deployment is excluded from the simulation. |
You can also create a quick analysis with the 'last 7 days' filter to check whether the metric has data for the last 7 days. |
Missing recent historical data. | Data for one or more of the required metrics is not available for simulation. |
|
Prediction error. | This message is displayed due to intermediate errors. | Run the simulation again. If the issue persists, contact BMC Support. |
Entity type is not supported. | A What-if Simulation can simulate growth only for the Kubernetes deployments. You cannot simulate for any other entity. When you try to simulate using a system identifier of an incorrect entity, this warning is displayed. | Exclude the deployment from the simulation and run the simulation again. |
No data available. | Data is not available to complete the simulation. | Check whether the ETL has failed to collect data. Check the ETL logs for troubleshooting. |