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
Typo in path?? #94
Comments
Hello @chucky2305, You’re right, the path hasn’t be updated with Symfony 4 new directory name. Can you create a PR to fix it or do you want me to do it? Thank you! |
I can create it tomorrow. Is there a way I can ask you a few questions
about this all? Though I fixed the path in my local environment I could not
get the logs into elasticsearch. The error logs of logstasj itself say that
logstash can't connect to the defined output target (in my case
elasticsearch)
Vincent Composieux <notifications@github.com> schrieb am Mo., 22. Okt.
2018, 19:01:
… Hello @chucky2305 <https://github.com/chucky2305>,
You’re right, the path hasn’t be updated with Symfony 4 new directory
name. Can you create a PR to fix it or do you want me to do it?
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AECBhqW-UsbXXMtnvNhsFmVAksoHPX8Kks5unfnLgaJpZM4XzaEh>
.
|
Hello, This part is strange and I think it’s specific to your environment because it works for me. Moreover, I am using Maybe you could have a look on elk’s repisotory issues? |
Fixes log directory (without "s") when using Symfony4 (fix #94)
Is there a typo in the path? I added "comments" in the code examples
docker-compose.yml
logstash.conf
The text was updated successfully, but these errors were encountered: