keystone.guru
keystone.guru copied to clipboard
[Heatmaps] Determine index mapping format
Also check in the mapping and queries to generate the index template, initial index, write alias, ILM policy etc.
Note that we want to take into account the following:
- Player deaths
- Killed enemies
- Cast spells
- Any other event
Gist of it is, all of these events need to be put in a single index so we can filter on them. Probably need to add a root object with context data or something
- @timestamp
- run_id
- challenge_mode_id
- key_level
- affix_id[] # array
- successful (bool)
- start
- end
- duration_ms
- pos_x
- pos_y
- event_type (death, killed enemy, etc)
- player
- id?
- class_id
- race_id
- # talents For later?
- context
// whatever data the event requires, see below
Contexts Player death event:
- spell_id? (which spell killed this player)
Enemy killed event
- npc_id
Cast spell
- spell_id
For nested objects ENSURE that we can properly filter on them. We want to index pretty much every field (which is the default?) and be able to search on it at some point in time.