-
Notifications
You must be signed in to change notification settings - Fork 482
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
Add logging for prometheus operator in TargetAllocator's config generator #2329
Add logging for prometheus operator in TargetAllocator's config generator #2329
Conversation
How busy were the logs when you enabled this? could you add some samples ones to the PR description? |
Thanks @jaronoff97. The logs were not busy. Since it is mostly only for invalid cases like the one in the description. Please help with merging this PR if all looks good. |
…hmichandrashekar/opentelemetry-operator into rashmi/prom-operator-logging
@jaronoff97 @frzifus - Please help get this merged, as I dont have permissions. Thanks! |
LGTM @jaronoff97 has to click :) |
Sorry I am on PTO today, but can merge real quick :) |
Thanks so much @jaronoff97! |
…ator (open-telemetry#2329) * add logging for prometheus operator * adding yaml for changelog * Adding tracking issue
Description:
Adding a feature - Currently, the prometheus operator logs, if any, are not visible from the targetallocator. This change enables error logging from prometheus-operator
Testing: Tested that logs that are returned by prometheus operator are logged to stdout
Sample logs -