-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gelf: support HTTP authentication #9355
Comments
@arvidvillen the |
Has a feature request been open for |
Yes, it is already linked in the description and apparently @arvidvillen is working on it so as soon as it's released we can un-freeze this one and implement it. |
The enhancement has been done on the upstream library, it will be available on 1.15.0 wich is not yet publshed. |
Hi @arvidvillen the new version of Will you still willing to implement this for Quarkus ? |
Description
When configuring Amazon Elasticsearch Service with public access and you don't want to configure IP based security it is recommended to use HTTP authentication and it would be nice if
quarkus-logging-gelf
supported that.Implementation ideas
Even if its not very clear in the documentation it seems that the extension supports HTTPS by setting
quarkus.log.handler.gelf.host
to something like https://example.com/, however adding the credentials like https://username:[email protected]/ does not work.Additional note
See mp911de/logstash-gelf#194
The text was updated successfully, but these errors were encountered: