quarkus-logging-manager icon indicating copy to clipboard operation
quarkus-logging-manager copied to clipboard

Quarkus extension that allows you to view the log online and change log levels using a UI

Results 14 quarkus-logging-manager issues
Sort by recently updated
recently updated
newest added

Bumps [quarkiverse-parent](https://github.com/quarkiverse/quarkiverse-parent) from 10 to 12. Release notes Sourced from quarkiverse-parent's releases. 12 What's Changed Bump impsort-maven-plugin from 1.7.0 to 1.8.0 by @​dependabot in quarkiverse/quarkiverse-parent#66 Format and import sort should...

dependencies

Bumps `quarkus.version` from 2.11.2.Final to 2.15.0.Final. Updates `quarkus-bom` from 2.11.2.Final to 2.15.0.Final Release notes Sourced from quarkus-bom's releases. 2.15.0.CR1 Major changes #29490 - SmallRye GraphQL 1.9.0 #29323 - Support filtering...

dependencies

Hi `quarkiverse/quarkus-logging-manager`! This is a one-off automatically generated pull request from LGTM.com :robot:. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result...

It would be nice if this extension had a `docs/` module so it could be included in the Quarkiverse docs website

Clicking this icon ![screenshot](https://user-images.githubusercontent.com/22860528/142934037-c1169f98-cb18-4004-ac9f-643100475d6c.png) responds with: ```json {"code":"NOT_FOUND"} ``` but I expect it to bring me back to Dev UI overview. Happens with both Quarkus 2.4.2 and 2.5.0.

Using ``` quarkus: logging-manager: openapi: included: true ``` and ``` io.quarkiverse.loggingmanager quarkus-logging-manager 2.1.0 ``` (also with runtime) I get: ``` java.lang.RuntimeException: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors...

Hi , As per current implementation , application packages are displayed as separated entries with their corresponding Log level. Is there any way, we can group them in tree hierarchy....

Hello, my swagger-ui shows warnings: ``` { "messages": [ "attribute paths.'/q/logging-manager'(get).responses.200.description is missing", "attribute paths.'/q/logging-manager/levels'(get).responses.200.description is missing" ], "schemaValidationMessages": [ { "level": "error", "domain": "validation", "keyword": "oneOf", "message": "instance failed...

from the UI and REST API, we should be able to add logger at runtime. ex : I could have : org.abc.database.level=ERROR but I want to add org.abc.label=debug I didn't...

enhancement

**As a user, I want to be able to restore log levels, so everything is back to how it was configured when the service started** Notes: - If someone else...

good first issue