@narayanaraov,   The problem appears to occur since the scm prepare script cannot tail the agent log.  This leads to the Wizard in Cloudera Manager to believe that the installation did not work properly.   See the error in the log snippet you provided:   tail: tail: cannot open '/var/log/cloudera-scm-agent//cloudera-scm-agent.log' for reading: No such file or directory cannot open '/var/log/cloudera-scm-agent//cloudera-scm-agent.log' for reading: No such file or directory   Check to see if the log file exists.  If it does not, that indicates that the agent may not have been able to start.  Try starting the agent manually on that host with "service cloudera-scm-agent restart"   Then, check /var/log/cloudera-scm-agent/cloudera-scm-agent.log again and see if it exists and if there are any errors in it.   Since we see in your log snippet that a tail of "/var/log/cloudera-scm-agent//cloudera-scm-agent.out " was successful, it is odd that the agent log didn't exist unless the agent process existed unexpectedly ... View more

@PSG01   No problem. Check out this documentation for some background on where the charts data comes from:   https://www.cloudera.com/documentation/enterprise/latest/topics/cm_dg_chart_time_series_data.html   metrics are stored in the Host Monitor and Service Monitor.  The data used in chart building is avaiable via the tsquery results.  The actual data is stored in leveldb files on disk (by default in /var/lib/cloudera-host-monitor and /var/lib/cloudera-service-monitor)   If you wish to view the metrics in JSON format you can click on the properties icon in the chart and choose "Export JSON"   -Ben ... View more

@Alexios,   This is the current documentation for Cloudera Manager Roles:   https://www.cloudera.com/documentation/enterprise/latest/topics/cm_sg_user_roles.html   Let us know if you have any questions.   -Ben ... View more