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 level can not be changed via MaintenanceWeb UI #29

Open
H4llJ0rdan opened this issue Mar 16, 2021 · 5 comments
Open

Log level can not be changed via MaintenanceWeb UI #29

H4llJ0rdan opened this issue Mar 16, 2021 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@H4llJ0rdan
Copy link

H4llJ0rdan commented Mar 16, 2021

Describe the bug
Log level can not be changed via MaintenanceWeb UI.

To Reproduce
Steps to reproduce the behavior:

  1. Start Moryx-Application with MaintenanceWeb installed Moryx.Runtime.Maintenance.Web package.
  2. Go to 'http://127.0.0.1/maintenanceweb/index.html#/log'
  3. Click on 'Filter by log level: ' and change it to 'trace'
  4. Do actions which should produce trace-logs
  5. See that they are not logged.

Expected behavior
Log level should be changeable via web UI.

Environment:

  • Browser: Microsoft Edge Version 89.0.774.54 (Official build) (64-bit)
  • OS: Windows10

Additional context
As a work around it is possible to change the log level in the config file manually.

@H4llJ0rdan H4llJ0rdan added the bug Something isn't working label Mar 16, 2021
@Toxantron
Copy link
Member

@mmarkwort can you take a look at this?

@mmarkwort
Copy link
Collaborator

I'll have a look

@dbeuchler
Copy link
Member

I checked this. In debug (without any security) it is possible without any problems. In normal dev environment the following error occures:

Access to fetch at 'http://computerName/loggers//appender/1' from origin 'http://localhost:8081' has been blocked by CORS policy: Method DELETE is not allowed by Access-Control-Allow-Methods in preflight response.

I remember we had several cors problems, are they completley fixed? @mmarkwort do you have any idea?

@dbeuchler
Copy link
Member

@mmarkwort If I change the API to Post instead of Put it works as expected. Maybe some CORS configuration missing?

@Toxantron
Copy link
Member

I think we fixed them, yes. Did you check the preflight response in chrome?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants