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

Fix/3286 #3369

Merged
merged 5 commits into from
Mar 17, 2015
Merged

Fix/3286 #3369

merged 5 commits into from
Mar 17, 2015

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Mar 17, 2015

Fixes #3286

Allows 'date' as a compatible field type for the min and max aggregation. Beyond adding 'date' to the field type filter, field formatters needed to support metric values that are dates. Now, when a metric agg runs on a date field, the formatter for that field is used on the metric value.

@panda01
Copy link
Contributor

panda01 commented Mar 17, 2015

LGTM.

One thing though, why not just add the date field type to the average too?

@jimmyjones2
Copy link
Contributor

If you're adding average, probably makes sense to add percentile, standard deviation etc too. eg. want to analyse how closely events happened to a target date

@spalger
Copy link
Contributor Author

spalger commented Mar 17, 2015

I don't think average or std deviation will produce useful data. Percentiles, maybe. I'll check it out

spalger added a commit that referenced this pull request Mar 17, 2015
@spalger spalger merged commit 7dbb084 into elastic:master Mar 17, 2015
@spalger
Copy link
Contributor Author

spalger commented Mar 17, 2015

Merged this for now to get the bootstrap fixes in.

@spalger spalger deleted the fix/3286 branch July 31, 2015 04:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Metric panel should allow max(@timestamp)
3 participants