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

Log warnings with kamelets #2395

Closed
orpiske opened this issue Jun 11, 2021 · 3 comments
Closed

Log warnings with kamelets #2395

orpiske opened this issue Jun 11, 2021 · 3 comments
Assignees
Labels

Comments

@orpiske
Copy link
Contributor

orpiske commented Jun 11, 2021

When using Kamelets I have these on the logs. I think we need to investigate this:

2021-06-11 11:31:05,455 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.log.console.json.pretty.print" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2021-06-11 11:31:05,455 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.log.console.json" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
@orpiske orpiske added area/kamelets area/observability Logging, monitoring and tracing labels Jun 11, 2021
@orpiske orpiske self-assigned this Jun 11, 2021
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@orpiske
Copy link
Contributor Author

orpiske commented Oct 22, 2021

This issue has been automatically marked as stale due to 90 days of inactivity. It will be closed if no further activity occurs within 15 days. If you think that’s incorrect or the issue should never stale, please simply write any comment. Thanks for your contributions!

I haven't been able to check that yet, so I'm keeping it opened for now (unless someone can verify / fix).

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant