Analytics does not work.
This article describes how to collect the minimum required information for Analytics on a CJP environment so that it can be efficiently troubleshooted.
If the required data is bigger than 50 MB you will not be able to use ZenDesk to upload all the information. On this case we would like to encourage you to use our upload service in order to attach all the required information.
- CloudBees Jenkins Platform (CJP)
- Operations Center (OC)
- Client Master (CM)
[ ] Confirm the version of Elasticsearch being used
[ ] Upload the config/elasticsearch.yml
[ ] Support bundle from OC and one CM
[ ] Test connection screenshot from OC
[ ] Proxy Configuration from CM and OC
[ ] CM config.xml
[ ] Elasticsearch quick health check
[ ] Elasticsearch logs
A support bundle from both OC and one of the CMs which is supposed to report information to Elasticsearch. Please, follow the KB below in case you don’t know how to generate a support bundle.
Go to Manage Jenkins -> Configure Analytics and hit the button Test Connection. After it, take a screenshot.
Go to the CM and OC and take a screenshot of the Proxy configuration you can find under Manage Jenkins -> Manage Plugins [Advanced tab]. Notice, that if you are using a Proxy at OC level, then you need to add the hostname of the Elasticsearch instance in the Non Proxy host section. i.e:
It is possible to access to the CM config.xml from OC UI. You just need to add at the end of the item URL
config.xml. i.e http://<OC_URL>/job/Master-1/config.xml
<com.cloudbees.opscenter.server.model.ManagedMaster plugin="firstname.lastname@example.org"> <actions/> <description/> <id>0</id> .... <com.cloudbees.opscenter.analytics.MasterReportingProperty plugin="email@example.com"> <enabled>true</enabled> </com.cloudbees.opscenter.analytics.MasterReportingProperty> ...
From OC machine launch the
curl command below and provide the output on the support ticket.
- The port is by default
Attach to the support ticket the logs from elasticsearch you can usually find under