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

Docs discrepancy in 'Change the index name' vs filebeat.reference.yml #34112

Closed
brsolomon-deloitte opened this issue Dec 23, 2022 · 4 comments
Closed
Labels
request-discuss Label added to request the creator to create a topic in discuss Stalled Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@brsolomon-deloitte
Copy link
Contributor

From https://www.elastic.co/guide/en/beats/filebeat/current/change-index-name.html#change-index-name:

output.elasticsearch.index: "customname-%{[agent.version]}"
setup.template.name: "customname"
setup.template.pattern: "customname-%{[agent.version]}"

From https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-reference-yml.html#filebeat-reference-yml (abridged):

output.elasticsearch:
  index: "filebeat-%{[agent.version]}"
setup.template.name: "filebeat-%{[agent.version]}"
setup.template.pattern: "filebeat-%{[agent.version]}"

There is a key difference here that is not explained by the docs. In the first example, the setup.template.name is not suffixed with the agent (filebeat) version, whereas in the second case, it is. As the agent versions are upgraded over time, this causes a difference in behavior where either (scenario 1) the same-named template is overwritten or (scenario 2) a new index template is created for each version.

Is it possible these two docs sources could be reconciled?

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 23, 2022
@belimawr belimawr added request-discuss Label added to request the creator to create a topic in discuss Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Jan 13, 2023
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 13, 2023
@botelastic
Copy link

botelastic bot commented Jan 13, 2023

Thank you very much for creating this issue. However, we would kindly like to ask you to post all questions and issues on the Discuss forum first. In addition to awesome, knowledgeable community contributors, core Beats developers are on the forums every single day to help you out as well. So, your questions will reach a wider audience there, and if we confirm that there is a bug, then you can reopen this issue with the new information or open a new one.

@botelastic
Copy link

botelastic bot commented Jan 13, 2024

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 13, 2024
@botelastic botelastic bot closed this as completed Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request-discuss Label added to request the creator to create a topic in discuss Stalled Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

No branches or pull requests

3 participants