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

Don't write diagnostic/informational info to STDERR #14

Closed
nblumhardt opened this issue Jan 14, 2019 · 1 comment
Closed

Don't write diagnostic/informational info to STDERR #14

nblumhardt opened this issue Jan 14, 2019 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@nblumhardt
Copy link
Member

Currently when sqelf starts, it prints some useful info to STDERR. Seq interprets this as event output and warns that it's not valid CLEF.

@nblumhardt nblumhardt added the enhancement New feature or request label Jan 22, 2019
@nblumhardt
Copy link
Member Author

Alternatively, this could be triggered using a --verbose flag or similar.

@nblumhardt nblumhardt added this to the 1.0.0 milestone Jan 22, 2019
nblumhardt added a commit that referenced this issue Jan 22, 2019
* Initial app packaging (WIP)

* Image rename

* Toolchain is Gnu

* Use alternative capabilities: configuration schema

* Install Rust in setup.ps1

* Install step rather than init step

* Fix path

* Fix name of gelfAddress setting

* Output verbose logs from cargo build

* Continue on errors so that cargo output is visible

* Redirect cargo's STDERR

* Write events to STDERR as valid CLEF

* Very simple pygelf example

* Use grayscale Seq logo for package icon

* Publish to NuGet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant