Cost Optimizer Troubleshooting

Adding a Cloud Account

If you are unable to add a cloud account, ensure that the credentials are valid and validate that the user or role assigned with the credentials has the correct permissions (see Cloud Overview > Minimum Permissions for Public Clouds). If the cloud account is a cloud master account, all child accounts must have AWS IAM role as Optimizer. This role must have the same permissions as described in the Minimum Permissions for Public Clouds section.

Costs for Private Clouds are not Displayed

If the Cost Optimizer Dashboard does not display costs for private clouds (vCenter, OpenStack, and Kubernetes), verify the following:

  • Price is specified in the Price field when adding instance types.

  • Cost is entered in the Cost field when adding storage types.

See Instance Types Settings and Storage Types Settings for additional context.

Cost by Organization Hierarchy Report is not Displayed

If the Cost by Organization Hierarchy report (applies to MasterAWS and GCP accounts only) is not visible, ensure that the Enable Reporting By Org Structure is toggled to On when adding a cloud. See Configure an AWS Cloud for more details. You must set the toggle to On to cause Cost Optimizer to import the cost hierarchy created in the cloud provider portal. 

Incorrect Numbers in Cost by Cost Group Type Report

If the Cost by Cost Group Type (Department) report displays incorrect costs for a specific cost group type, verify that the billing units are mapped correctly to the cost group type.

Inventory Types not Displayed

Inventory is only collected for regions that are explicitly added while setting up clouds. If you do not see expected inventory types (VMs, Kubernetes Workloads, Storage Volumes, and Services), verify that regions you added contain the inventory on the cloud. 

No Rightsizing Recommendations are Displayed

Rightsizing recommendations are governed by the Settings tab in the Admin area. Review the values in this tab, in particular, review the value set for the Min. Running Days field.

Kubernetes Troubleshooting

Based on the error message that you see in the UI, you could perform basic troubleshooting steps if you have access to both the Kubernetes setup and to the CloudCenter Suite:

IssueError Reference Location
Errors returned by the Kubernetes clusterGo to the Kubernetes dashboard and look for the event messages and login to the pod that you created for the CloudCenter Suite.
Kubernetes cluster API interaction issuesLogin to Kibana (Monitor Modules > View Logs in Kibana) and look for error messages in logs with the text "cloudcenter-blade".
Orchestration or lifecycle issues

Login to Kibana (Monitor Modules > View Logs in Kibana)  and look for error messages in logs with the text "cloudcenter-cco".

You may find the following warning message in the Kubernetes cloudcenter-cco logs – you can safely ignore this message as it does not impact product functionality.

WARNING!!! The linux bootstrap URL might be valid: http://build-rel.cliqr.com/..../bootstrap-cliqr-init.sh. If Workload Manager cannot access the file, all deployments would fail!
Model, manage, deploy issuesLogin to Kibana (Monitor Modules > View Logs in Kibana) and look for error messages in logs with the text "cloudcenter-ccm-backend" or "cloudcenter-cloud-setup".

For additional details, refer to the following documents:

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved