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

Wrong mapping fields names for webtracking with ElasticSearch #26

Open
ghost opened this issue Jun 20, 2018 · 1 comment
Open

Wrong mapping fields names for webtracking with ElasticSearch #26

ghost opened this issue Jun 20, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented Jun 20, 2018

In the doc (https://www.app-metrics.io/reporting/reporters/elasticsearch/) it is recommended to create an index and to send the mapping :

Add an index and the document mappings to Elasticsearch using the default mappings provided in the github repository

But when i send this command to ES :

PUT appmetricssandbox/_mapping/timer?update_all_types
{
  "properties": {
    "tags.env": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.exception": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.app": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.route": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.server": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.item": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.client_id": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.http_status_code": { 
      "type":     "text",
      "fielddata": true
    },
    "tags.health_check_name": { 
      "type":     "text",
      "fielddata": true
    }
  }
}

I get this error for ES :

{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Field name [tags.env] cannot contain '.'"
}
],
"type": "mapper_parsing_exception",
"reason": "Field name [tags.env] cannot contain '.'"
},
"status": 400
}
@alhardy
Copy link
Collaborator

alhardy commented Jun 22, 2018

The ES reporter has fallen behind since breaking changes in ES were introduced.

I'm struggling to maintain all reporters on my own outside the those I use myself in production.

Any help appreciated.

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

No branches or pull requests

1 participant