-
Notifications
You must be signed in to change notification settings - Fork 8
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
Nothing being received in Seq? (Laravel / Gelf / Seq) #79
Comments
Hi @azcoppen Thanks for getting in touch, and for the detailed information! I was able to reproduce your issue. The reason why I listed Please let me know, or close this issue, if this also fixes it for you! Here is my
Cheers, |
@larenelg Thanks for the comprehensive and speedy response! Let me run it and see. Going to have a happy dev team if it does! |
@larenelg You're a legend. Had to switch the default host from '127.0.0.1' to 'seq-input-gelf' though when using docker. Would be great to have a Monolog plugin for the Seq HTTP API. Most devs i know use an external SaaS (pricey) or Graylog (requires Mongo and Elastic). For others who are looking to implement this, had to make some changes to
|
Thanks for sharing that config @azcoppen - I hope you don't mind if we add a "logging from Laravel" section in our docs with similar config as an example (with due credit, of course!). It's been a while since I've built something using Laravel :) RE: a Monolog plugin - bandwidth is a little thin on our team at the moment, but it does sound worthwhile! I might have a go at it myself, but if you are feeling like dabbling, here's an easy-to-follow tutorial on how to make a custom Seq Input Apps :) https://docs.datalust.co/docs/writing-custom-inputs |
Be my guest! It's a bit thin on the ground in terms of docs tbh. This was the only package i found, but it's abandoned: https://github.com/msschl/monolog-seq-handler I don't want to have to install Mongo/ES for Graylog - we need a nice team solution where we can watch API clients in real time, not have to SSH in for logs, and not send data across the net (even queued). It makes it a whole new thing IMO. Particularly as you can log to the same place from different types of apps (e.g. Electron, Django, NoSQL DB etc). |
Attempting to send errors from Laravel framework through its Logging engine as GELF to Seq.
Docker compose setup:
Ports are up:
Docker ps:
Container:
This works and appears in Seq.
This returns fine but does not appear in Seq (no STDOUT either, nothing when listening on the port, no error):
Attempting to use this package: https://github.com/hedii/laravel-gelf-logger also fails.
config/logging
in Laravel:Logs from Seq (no errors)
From within the container:
Logs from seq-input-gelf:
The text was updated successfully, but these errors were encountered: