Skip to content

Overly aggressive guidance on deleting Beats indices to refresh Kibana data #1595

Open
@rseldner

Description

@rseldner

Type of issue

Other

What documentation page is affected

https://www.elastic.co/docs/reference/beats/auditbeat/auditbeat-template

What happened?

I find this Force Kibana to look at newest documents section a bit bizarre and wonder why we include it at all. It may be better to remove it entirely or reframe it in a more appropriate context.

The issue of Kibana not displaying recent documents is typically caused by time filters, outdated index patterns, or ingestion delays; not by the presence of old documents. Recommending deletion of the auditbeat-* entirely seems unnecessary for the purpose of seeing updated documents.

The same concern applies to the equivalent docs for the other Beats products as well.

examples:
https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-template#force-kibana-new
https://www.elastic.co/docs/reference/beats/filebeat/filebeat-template#force-kibana-new

Additional info

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:IngestIssues owned by the Ingest Docs TeamdocumentationImprovements or additions to documentationinvalidThis doesn't seem rightsource:webIssues originating from the elastic.co docs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions