Event

A telemetry event follows the Elastic Common Schema's event.* field set as it stands, rather than a MealStack version of it, so events land in any ECS-aware store without a mapping. Only the fields the app uses are listed here; the rest of ECS event.* applies unchanged. Counts and timings only; never an ingredient, a plate or a figure that would say what a person ate.

Fields

1. event.action core keyword required

   The app's name for what happened, lower case with underscores, the same string the app's telemetry has always sent.

   Valuesmeal_loggedmeal_skippedday_type_changedstack_switchedstack_movedstack_keptstack_usedplan_importedplan_file_openedmeal_template_addedmeal_count_changedplan_editedonboarding_stepsettings_changedhealth_sync

   Examplemeal_logged

2. event.category core keyword

   The ECS category the action falls under; the app's actions are all process events from the person's point of view, or configuration for settings.

   Exampleprocess

3. event.outcome core keyword

   success, failure or unknown, as ECS defines them.

   Examplesuccess

4. event.dataset extended keyword

   mealstack.app, mealstack.widget, mealstack.coach.

   Examplemealstack.app