Error Running Curator Rollover method


(Al) #1

I'm currently collecting metricbeat data from many systems that gets stored in an index with the format of 'metricbeat-YYYY.mm.dd'. When I attempt to test my curator action to run a rollover, I get the following error:

curator.exceptions.ConfigurationError: Configuration: options: Location: Action ID "3", action "rollover": Bad Value: "(could not determine)", expected str for dictionary value @ data['new_index']. Check configuration file.

Below are some other relevant details of my current configurations

Version of elasticsearch-curator: 5.4
Version of Elasticsearch: 6.1

Elasticsearch output config that writes the metricbeat data:

elasticsearch {
  id => "es_out_metricbeat"
  document_id => "%{[@metadata][fingerprint]}"
  hosts => ["http://localhost:9200"]
  index => "metricbeat-%{+YYYY.MM.dd}"
  manage_template => false
  upsert => true
}

The first part of my metricbeat index template (mappings omitted due to size):

{
  "order": 1,
  "index_patterns": [
    "metricbeat-*",
    "*-*-metricbeat-*",
    "metricbeat*"
  ],
  "settings": {
    "index": {
      "codec": "best_compression",
      "mapping": {
        "total_fields": {
          "limit": "10000"
        }
      },
      "refresh_interval": "10s",
      "number_of_routing_shards": "30",
      "number_of_shards": "1"
    }
  },
  "aliases": {
    "metricbeat": {}
  }
}

My actions file contains:

actions:
  1:
    action: rollover
    description: >-
      Rollover the metricbeat indices, which should be in the
      form of prefix-000001 (or similar), or prefix-YYYY.MM.DD-1.
    options:
      disable_action: False
      name: metricbeat
      conditions:
        max_age: 10s
      extra_settings:
        index.number_of_shards: 1
        index.number_of_replicas: 1
        aliases:
          metricbeat: {}
      continue_if_exception: False

Would anyone know what my issue might be? I appreciate any help!


(Aaron Mildenstein) #2

For rollover, it automatically preserves the alias, so this part is redundant, and may result in a bad API call. If you were adding to another alias, then you'd add it here.

Beyond that, the action file provided doesn't match the error message. The error message says that Action ID "3" has a misconfiguration. But the pasted action file segment shows:

Why the discrepancy? It appears there's a misconfiguration, but the pasted configuration seems different in at least that regard.


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.