Skip to content
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

Extensive documentation #25

Open
3 tasks
bzikarsky opened this issue Oct 16, 2014 · 6 comments
Open
3 tasks

Extensive documentation #25

bzikarsky opened this issue Oct 16, 2014 · 6 comments

Comments

@bzikarsky
Copy link
Owner

Currently the documentation is almost non existent. This should be changed.

  • Explain architecture with comprehensive examples
  • Explain integration into monolog
  • Update README with links to new docs
@bzikarsky bzikarsky modified the milestone: 1.2 Oct 19, 2014
@bzikarsky
Copy link
Owner Author

ReadTheDocs viable?

@bzikarsky bzikarsky modified the milestones: 2.0, 1.2 Mar 9, 2015
@HMAZonderland
Copy link

Documenting things is never fun, I see. :-)

@bzikarsky
Copy link
Owner Author

Oh well... 🙁 -- Well deserved critism...

@drzraf
Copy link

drzraf commented Nov 28, 2019

If we assume a monolog config (README.md), it seems that sample configuration is larger than strictly necessary:

  • Why not using { type: gelf, publisher: {id: @id-of-publisher } }?
  • Couldn't ignore_error_transport be replaced by whatfailuregroup?

On a semi-related note, I found that simply authenticating to a Gelf endpoint (for OVH, using Tcp rather than Http), currently needs its own bundle instead of having a flexible processor for that purpose within gelf-php itself even though it's just about appending some data. There is that Logger::$defaultContext but I didn't see a way to hook it from monolog-bundle configuration.

@pscheit-lillydoo
Copy link

a monolog bundle configuration would be handy

@bzikarsky
Copy link
Owner Author

I haven't worked with Symfony/Monolog in quite some time, I'm happily welcoming PRs with better docs. :)

@bzikarsky bzikarsky removed this from the 2.0 milestone Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants