Investigate
Inspect events and customer cohorts
Check who performed a diagnostic event and save reusable customer groups for investigation or rollout targeting.
Teml’s Events and Cohorts views are supporting investigation tools. Use them to establish behavioral context around a customer problem, not as the default starting point for application analytics.
Inspect an event
Open Explore → Events, choose an event name, and review its recent volume and identified customers. If an event is missing, confirm the SDK sent it after identity was established and that the current project and time window are correct.
Open a customer from the triggerer list to compare the event with their errors, traces, replay, releases, and AI calls. Event volume alone does not explain an outcome.
Create a cohort
Open Explore → Cohorts and create a reusable customer group. Teml supports behavioral, property-based, and static definitions. Use a stable name that describes membership rather than the campaign that first needed it.
Choose Refresh after changing upstream data or when current membership is required immediately. Open the cohort’s members to validate representative customers before using it in a feature rollout or watched alert.
Deleting a cohort is destructive. Feature flags that target it stop matching those members, so remove or replace those dependencies first.
Keep definitions trustworthy
-
Prefer stable identity and normalized properties.
-
Avoid static lists when a behavioral or property definition expresses the rule.
-
Sample members after creation and after significant instrumentation changes.
-
Record why a cohort exists in its name or team runbook.