| 1234567891011121314151617181920212223242526272829303132 | [role="xpack"][testenv="platinum"][[ccr-auto-follow]]=== Automatically following indicesbeta[]In time series use cases where you want to follow new indices that areperiodically created (such as daily Beats indices), manually configuring followerindices for each new leader index can be an operational burden. The auto-followfunctionality in {ccr} is aimed at easing this burden. With the auto-followfunctionality, you can specify that new indices in a remote cluster that have a name that matches a pattern are automatically followed.==== Managing auto-follow patternsYou can add a new auto-follow pattern configuration with the{ref}/ccr-put-auto-follow-pattern.html[create auto-follow pattern API].  When you createa new auto-follow pattern configuration, you are configuring a collection ofpatterns against a single remote cluster. Any time a new index with a name that matches one of the patterns in the collection is created in the remote cluster,a follower index is configured in the local cluster. The follower index uses the new index as its leader index.You can inspect all configured auto-follow pattern collections with the{ref}/ccr-get-auto-follow-pattern.html[get auto-follow pattern API]. To delete aconfigured auto-follow pattern collection, use the{ref}/ccr-delete-auto-follow-pattern.html[delete auto-follow pattern API].Since auto-follow functionality is handled automatically in the background onyour behalf, error reporting is done through logs on the elected master nodeand through the {ref}/ccr-get-stats.html[{ccr} stats API].
 |