Objective
Implement end-to-end logging for a single Slack analytics event via Datamesh publisher, mapped to Datamesh principles. This issue will serve as a reference for aligning analytics event logging with Datamesh standards using the SearchHandler as the implementation target.
Scope
- Select a representative Slack event for logging (e.g., "search" action from SearchHandler.cs)
- Integrate event publishing to Datamesh using the Datamesh publisher pattern
- Add basic error handling and runtime logging to ensure reliability and traceability
- Snowflake-side validation is explicitly out of scope
Implementation Steps
- Review the existing SearchHandler.cs event logging
- Map the event schema and flow to Datamesh principles (ownership, discoverability, schema governance)
- Refactor or extend SearchHandler to produce an event via the Datamesh publisher
- Ensure logs are written when event is published or when failures occur (error handling)
- Test that the event appears correctly in Datamesh/Snowflake (event structure and schema match required definitions)
- Prepare implementation and documentation as a blueprint for further analytics event logging changes
Outcome
- One Slack event (search) is logged end-to-end and visible in Datamesh/Snowflake with the correct schema.
- Review completed and code ready to be used as a reference for other events.
Related:
- Epic KNOW-5832 (Datamesh standards)
Objective
Implement end-to-end logging for a single Slack analytics event via Datamesh publisher, mapped to Datamesh principles. This issue will serve as a reference for aligning analytics event logging with Datamesh standards using the SearchHandler as the implementation target.
Scope
Implementation Steps
Outcome
Related: