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

logs - log-level and json-format #2764

Closed
AllroundIT opened this issue Feb 16, 2024 · 2 comments
Closed

logs - log-level and json-format #2764

AllroundIT opened this issue Feb 16, 2024 · 2 comments
Labels
feature request Request for a non-existing feature

Comments

@AllroundIT
Copy link

We use a log server and it would be a great help if the log format was JSON. This would enable the log server to prepare the logs accordingly and they would be easier to read and find again.

In addition, in certain environments we are not interested in logs with the log level "debug" or "info", so it would be great if you could set the log level. This would also reduce the load on the log server, as the unnecessary logs would not arrive in the first place.

Currently, the "dynatrace operator" and "webhook" services already log out of the box in JSON format.

Unfortunately, "active gate" and "one agent" do not.

@luhi-DT
Copy link
Collaborator

luhi-DT commented Feb 19, 2024

Hi @AllroundIT, thanks for your input, as you said operator/webhook/CSI Driver are already logging in json format. We are also working on different log levels and how we can utilise them best, however this repo is focused on the Dynatrace Operator and its components (webhook, csi driver) and not on OneAgent and ActiveGate, therefore please open an RFE (request for enhancement) in our Dynatrace community. This way we can ensure your input is not missed :) Thanks!

@luhi-DT luhi-DT added the feature request Request for a non-existing feature label Feb 19, 2024
Copy link
Contributor

Thank you for opening a Dynatrace Operator Issue. We've identified and tagged the issue as a "Feature request".

Dynatrace reviews feature requests in the Dynatrace community rather than Github. This helps our team consolidate, rank, and prioritize important input like yours.

Please search for similar requests, collaborate, and ask questions using the link above. Remember to add the labels "kubernetes" and "dynatrace-operator" to help get the attention you deserve.

Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for a non-existing feature
Projects
None yet
Development

No branches or pull requests

2 participants