-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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 Microsoft OMS (Operations Management Suite) monitoring DaemonSet example #39538
Conversation
Hi @OguzPastirmaci. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@k8s-bot ok to test. |
Thanks for this PR. While it's great to have this in the examples, it would be even better to have it in the main site: https://github.com/kubernetes/kubernetes.github.io Feel free to do a PR there too and tag me into it. Thanks! |
Will do that one as well, thanks! |
@k8s-bot test this please |
[APPROVALNOTIFIER] Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/lgtm |
/approve @brendandburns: The parser is still strict, |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
I've noticed this daemonset example, but is it possible for the oms agent to augment the logging with kubernetes specific information such as pod name, namespace, tags, etc? A bit like https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter does. |
Adds example to deploy Microsoft OMS monitoring agents using Daemon Sets.