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

Have no settings for set custom rollover_alias #3779

Closed
MaxymVlasov opened this issue May 8, 2020 · 4 comments
Closed

Have no settings for set custom rollover_alias #3779

MaxymVlasov opened this issue May 8, 2020 · 4 comments
Assignees

Comments

@MaxymVlasov
Copy link

MaxymVlasov commented May 8, 2020

Hi!

I need to set custom rollover_alias how I did it in filebeat, but found that APM have no configuration for it.

I searching how it can be done and found that in template.go exist "lifecycle.rollover_alias": name, construction introduced in #2099. But I have no idea how I can use it.

So, this is or feature request or docs improvement request.

Here how it looks like in filebeat:

setup.ilm.rollover_alias: "filebeat-prod"

Use case

Now we use one EFK for all environments. Each environment have it own ILM policy with different settings.
So I need setup all indexes like this:

Otherwise, data from all envs will be mixed in one index.

But this not works for APM, so now I must use different APM-server versions in each environment.

@simitt
Copy link
Contributor

simitt commented May 14, 2020

Hi @MaxymVlasov, you are right that we currently do not support setting custom rollover_alias. If you depend on customizing the aliases you would need to manually set up ILM (rollover_aliases, policies and templates), disable the setup by APM Server (apm-server.ilm.setup.enabled=false) and configure the rollover aliases as indices in the output.elasticsearch.indices section.

I'll label this issue as enhancement request and investigate how much effort it would be to add support in the APM Server.

@MaxymVlasov
Copy link
Author

MaxymVlasov commented May 14, 2020

We also need ILM, because time to time we have logs/metrics peaks and get up to 10 more data in this periods, so day-by-day rotation is not works for us very well => curator not suitable solution.

In same time, I have many projects with +- same settings, so for me "Everything as Code" better than any manual work in long term.

@simitt
Copy link
Contributor

simitt commented May 29, 2020

This has been implemented with #3826. The configuration for rollover_alias is restricted to known strings or variable parts from observer.* that are known at setup time. (The same restriction applies for beats at the moment).

@MaxymVlasov
Copy link
Author

Thank you!

I will definitely try when v7.9.0 will be released.

@axw axw removed the [zube]: Done label Jun 3, 2020
simitt added a commit to simitt/apm-server that referenced this issue Jun 23, 2020
* Refactor ILM config loading and conditional index selection

* Make rollover_alias configurable and document it

closes elastic#3779
simitt added a commit that referenced this issue Jun 23, 2020
* Refactor ILM config loading and conditional index selection

* Make rollover_alias configurable and document it

closes #3779
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants