Thanks, Jessica. Knowing about config.js led me to find the problem. I had accidentally put the metricsPublicURL at assetConfig.servingInfo.metricsPublicURL instead of the correct assetConfig.metricsPublicURL in the master-config.yaml. Simple error, but I just couldn't see it. I've got metrics showing up now. I appreciate the help Jessica and BR!
-- Robert Wehner Return Path On Sun, Feb 21, 2016 at 7:08 AM, Jessica Forrester <[email protected]> wrote: > Can you check the contents of the config.js that is getting loaded in the > browser, make sure metricsPublicURL is in there and set correctly, that's > what the console is triggering off of to know to show the tab. > On Feb 20, 2016 10:30 PM, "Robert Wehner" <[email protected]> > wrote: > >> Good to know it is probably not my certificates. I don't see any red box >> or any indicator that the hawkular server is unreachable. Judging by this >> demo video (https://youtu.be/RMDX3YC0CSQ?t=1m2s), I was expecting to >> have a 'metrics' link on each pod's detail page, but don't see that either. >> >> >> -- >> Robert Wehner >> Return Path >> >> On Sat, Feb 20, 2016 at 2:32 PM, aleks <[email protected]> wrote: >> >>> >>> >>> Am 20-02-2016 01:10, schrieb Robert Wehner: >>> >>>> Thanks for your reply, BR. I am using self-signed certificates at the >>>> moment but I did follow these instructions to accept the >>>> metricsPublicURL certificate in my browser. In the browser I can see the >>>> Hawlular splash page with an image, some version info and "Metrics >>>> Service :STARTED". I can also see the "hawkular/metrics/status" endpoint >>>> in the browser. >>>> >>> >>> Okay, than at least the ssl isn't the problem. >>> >>> I turned up logging on origin-master to "--loglevel=8" hoping to see >>>> some debug info on the console's attempt to connect to hawkular, but >>>> didn't see anything clearly related. I do see SkyDNS responding to >>>> lookups for the "hawkular-metrics.openshift-infra.svc.cluster.local." >>>> service, and various controllers reporting in (but not changing >>>> anything). No errors or obvious errors about connections to hawkular. >>>> Are there other logs that would be more appropriate to look at? >>>> >>> >>> Do you have no data or do you have this red box with the message that >>> the hawkular server is not reachable? >>> >>> >>> Thanks again for you response. >>>> >>>> Robert >>>> >>>> -- >>>> Robert Wehner >>>> Return Path >>>> >>>> On Fri, Feb 19, 2016 at 4:20 PM, aleks <[email protected]> >>>> wrote: >>>> >>>> Hi. >>>>> >>>>> Am 19-02-2016 18:36, schrieb Robert Wehner: >>>>> >>>>> I am setting up an Origin 3.1 cluster with metrics as outlined at >>>>>> >>>>>> https://docs.openshift.org/latest/install_config/cluster_metrics.html >>>>> . >>>>> >>>>>> I >>>>>> think everything is running correctly, but I don't see any metrics >>>>>> in >>>>>> the console at all. >>>>>> >>>>> >>>>> Have you accept the certificate from the hawkular? >>>>> >>>>> >>>>> >>>> https://docs.openshift.org/latest/install_config/cluster_metrics.html#configuring-openshift-metrics >>>> >>>>> >>>>> The 'box' >>>>> >>>>> ### >>>>> If you are using self-signed certificates, remember that the Hawkular >>>>> Metrics service is hosted under a different hostname and uses >>>>> different certificates than the console. You may need to explicitly >>>>> open a browser tab to the value specified in metricsPublicURL and >>>>> accept that certificate. >>>>> >>>>> To avoid this issue, use certificates which are configured to be >>>>> acceptable by your browser. >>>>> ### >>>>> >>>>> This sentence means that you should call metricsPublicURL in your >>>>> browser on which you want to see the metrics. >>>>> >>>>> BR >>>>> Aleks >>>>> >>>> >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >>
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
