After deploying ELK stack, we have hit a snag where mapping visualisations are not rendering.
The URL that the end user browser attempts to contact is;
Is this expected behaviour?
Ideally I would like to refrain from white listing/pin-holing the access direct on the firewall and instead leverage the corporate proxy solution that is available here. It is possible that this should work and that we have an environment fault (such as proxy bypass etc). By default unless explictly bypassed, all external traffic should route via Proxy. Bit at a loss as to why this call from the browser is failing. Debugging tools show successful load of all other components of the interface, this is the exception to the rule which I believe is the root cause.
Appreciate any insight that can be provided for this issue.