Generate shorten kibana discovery url using internal kibana url

[alexku7]

Hello
We have two kibana endpoints.
The first one is the external url protected by some security proxy and requires a human activity in order to login.
The second one is internal and used by tools only for example ElastAlert

Is it possible to use the interl URL to generate the short Kibana URL but the final URL which will be sent in the alert will be with the External base url ?

For example
internal url : https://localhost
exteranl url: https://kibana-external.com

The elastalert will connect to https://localhost in order to generate the short url but the final generated url will be something like
https://kibana-external.com/app/r/s/yCR9H

[jertel]

I don't see how this would be possible. You would be asking the internal instance to map a shortened URL, but then asking an external instance to unmap that short URL, which it doesn't have any knowledge of.

[alexku7]

this is what I think
this is the single ELK instance but simply can be accessed by 2 different URL ( very common scenario I think)

if I understand correctly the API returns the locatorID so all whats needed is construct the final URL by adding the external URL and the /locatorID
Am I right ?

[jertel]

I see, so you only have one Kibana instance, but two ways to get to it. Thanks for clarifying.

Yes, you just need the dynamic query parameters to create the correct URL.

[alexku7]

can you explain pls ? Is it possible or need to develop the feature ?

[jertel]

I mentioned a possible solution earlier today:

you could write a custom enhancement that looks at the generated URL stored in the match, and swap out the hostname, before the alerter is invoked.

[alexku7]

Thank you