We have setup WSO2 API-M v2.1.0 with API-M Analytics v2.1.0 with Postgresql and HAProxy on CentOS. The API analytics reports are being shown as expected from the Publisher and the Store side and even the api availability from the Admin Portal.
This is a distributed set-up comprising separate publisher, store, key manager, traffic manager, gateway manager/worker and analytics. Consul service discovery is providing local DNS resolution.
On the gateway worker we have enabled log analyzer; also HAProxy is forwarding /portal and /shindig to the Admin Portal publisher node.
Also note the publisher was started on its api-publisher product profile, however this resulted in missing alert configurations, see jira issue.
This is easily resolved by reverting to the default profile; still none of the log analyzer links are being populated when logged into the Admin Portal application.
When attempting any of the Log analyzer links from the Admin Portal the browsers javascript console is displaying the following errors :
"Failed to preload gadget https://<HOSTNAME>/portal/store/carbon.super/fs/gadget/LiveLogViewer/index.xml."
and
"Detailed error: 503 Unable to retrieve spec for https://<HOSTNAME>/portal/store/carbon.super/fs/gadget/LiveLogViewer/index.xml. HTTP error 503"
From the analytics carbon console I can validate my gateway log analzyer configuration from the data explorer seen here
The docs seem to suggest the need to edit js code for the log analyzer??
