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

HWKALERTS-252 Fix wrong nanoseconds parsed time #317

Merged
merged 1 commit into from
Apr 5, 2017

Conversation

lucasponce
Copy link
Contributor

HWKALERTS-251 Fix wrong dot character on Elasticsearch alerter
HWKALERTS-247 Add an Elasticsearch intergation example

Please @jshaughn, could you review ?

This would be necessary for a potential 1.6.x. and metrics 0.26.x.

HWKALERTS-251 Fix wrong dot character on Elasticsearch alerter
HWKALERTS-247 Add an Elasticsearch intergation example
Copy link
Contributor

@jshaughn jshaughn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, so if I understand correctly, this PR addresses HWKALERTS-247,251,252? It seems OK, I only had the one question but that is mostly just curiosity. I can probably merge after you reply.

@@ -69,7 +69,7 @@
* Documents fetched from Elasticsearch need a date field to indicate the timestamp.
* This timestamp will be used in the queries to fetch documents in interval basis.
*
* If there is not defined a specific pattern under the trigger.context["timestamp.pattern"] it will follow the
* If there is not defined a specific pattern under the trigger.context["timestamp_pattern"] it will follow the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the change from the dot to the underscore? I think ES does not allow a dot but this is an hAlerting contect name, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because Elasticsearch 2.x version doesn't accept dot as part of field name.
And when storing a full alert, it might fail with context with dots.
It is fixed in upper versions but 2.x is the target used for OS deployments, so that's motivation.

@jshaughn
Copy link
Contributor

jshaughn commented Apr 5, 2017

Thanks, Lucas!

@jshaughn jshaughn merged commit 35ed7a9 into hawkular:master Apr 5, 2017
lucasponce added a commit that referenced this pull request Apr 5, 2017
HWKALERTS-251 Fix wrong dot character on Elasticsearch alerter
HWKALERTS-247 Add an Elasticsearch intergation example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants