NatLabRockies / NatLabRockies/api-umbrella
ElasticSearch Index Name + Date type
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 373
- PR merge metrics
- No merged PRs in 30d
Description
I noticed api-umbrella used a different name for a new month's index: Instead of api-umbrella-logs-v1-2017-07 like in previous version the index was named api-umbrella-logs-write-2017-07
Is this expected behaviour? I couldn't find changes in the release notes.
It seems like at least some users are directly accessing the ES database, so a change in the naming could break things here.
Also the data type of the request_at field is long instead of date, so it's not possible to filter by date – and the analytics page in the admin backend return error 500.
I'm using api-umbrella 0.14.2 and ElasticSearch 2.3 managed by AWS.
@GUI
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the index naming and request_at mapping with api-umbrella 0.14.2 and Elasticsearch 2.3, then inspect the generated index mappings and the admin analytics failure. Done means the expected index name is established or corrected, request_at supports date filtering, and the analytics page no longer returns HTTP 500.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100