Add configuration for serverBasePath and serverRequestHeader

[anmoel]

Hi,

we split our frontend- and backend-systems and we want to host the elastalert2 server behind an api-gateway.
This api-gateway hosts many APIs so we need a basePath option for selecting the elastalert server.
Additional we must add custom headers on each request, so we can authenticate against our api-gateway.

i will prepare a pull-request for both.

regards
André

[Karql]

Hi,

Why do you want to expose elastalert2-server with an api-gateway?
Only for elastalert-kibana-plugin or do you have another use case?

If only for plugin imo there is no such need.

Plugin does not make requests directly to elastalert2-server but first make request to kibana and kibana proxied it to elastalert2-server.

IMO you should expose only kibana and keep elasticsearch and elastalert2-server internally.

This approach is more secure.

Best regards,
Mateusz

[anmoel]

hi @Karql ,

kibana is an frontend application and not behind the api-gateway. The api-gateway only support REST calls.
so the api-gateway is between the kibana server and the elastalert2-server / elasticsearch server

[Karql]

Is there something in front of kibana like reverse-proxy?

I don't see any reason why kibana it could not be behind api-gateway.

[anmoel]

the api gateway only supports REST conform APIs and not all HTTP requests. sessions and other http features are not supported
Additional Kibana should not reachable for all Users like this page

I implemented both optional parameters in PR #35.

[Karql]

Released: https://github.com/Karql/elastalert-kibana-plugin/releases/tag/1.6.0