Dynamic Index Names

alerting

#1

Looks like this was added to 1.0 which is great news however I have 2 questions

  1. It doesn't appear that this works in the "path" of an "http" input. Is that correct? Will there be any consideration to adding that in the future so that we can easily monitor an ES time series from a different cluster?
  2. Our indexes roll at midnight US/Mountain time (not UTC). I don't believe there is any support for that when using dynamic index names short of subtracting an offset (which won't really work when considering DST). Is that correct and is there any alternative I'm not thinking of (short of managing some aliases ourselves)?

Thanks!


(Uri Boness) #2

Heya,

It doesn't appear that this works in the "path" of an "http" input. Is that correct? Will there be any consideration to adding that in the future so that we can easily monitor an ES time series from a different cluster?

correct, currently it's only available on the search input, search transform and index action. But yes we already discussed the option available for remote es communication. Will probably not be as part of the http input (as it's too generic to introduce it there).. it fits more in a new dedicated es-http input... we'll work on that

Our indexes roll at midnight US/Mountain time (not UTC). I don't believe there is any support for that when using dynamic index names short of subtracting an offset (which won't really work when considering DST). Is that correct and is there any alternative I'm not thinking of (short of managing some aliases ourselves)?

yea... good one. So indeed at the moment now is UTC. But I see your point, and it makes sense to enable setting the TZ for "now". We'll add it in.

Thx for the valuable feedback!


(system) #3