-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[ES] enhance es mapping for event #1379
[ES] enhance es mapping for event #1379
Conversation
Can a kubernetes member verify that this patch is reasonable to test? If so, please reply with "@k8s-bot ok to test" on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands will still work. Regular contributors should join the org to skip this step.
If you have questions or suggestions related to this bot's behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
|
6bd3a10
to
89dec61
Compare
@googlebot i run it correctly in my laptop. |
I don't know why the test |
it turns out that memory is out and something like |
e343639
to
e30c5e9
Compare
e30c5e9
to
a5f0ccc
Compare
That's an interesting approach, i solved that slight differently in #1313 |
Can anyone review it? @AlmogBaku? |
I think it's now redundant after #1313
If you see any reason to implement it this way other than the method i
used, can you elaborate?
…On Wed, 23 Nov 2016 at 15:20 Piotr Szczesniak ***@***.***> wrote:
Can anyone review it? @AlmogBaku <https://github.com/AlmogBaku>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1379 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGCpvHiwkgtYP5Mr731TDDjMSC1hZIyks5rBD2FgaJpZM4Kw6g_>
.
|
closing per @AlmogBaku comment |
This PR adds support for adding more info for analyze events in ElasticSearch. This PR adds
EventType
,EventKind
,EventReason
andEventMessage
as tags and thus allows us to query based on them. Such as, what are the warning events in last two hours. When does the cluster emitsFailedScheduling
events.This PR also adds the namespace tag info when the event is of Pod kind.
This change is