Change Details

==== Background Coming out of a recent spike T345439 (Prototype API for Submitting Core Interaction Events), we have an initial proposal for an API that specifies some preliminary methods for submitting events against the newly drafted, to-be-merged [[ https://gerrit.wikimedia.org/r/c/schemas/event/secondary/+/952252 | core interactions schemas ]] (See T345439#9217684). ==== Developer notes Presumably this goal entails documenting the proposed API and detailing the process by which a given instrument managed by a feature team can use the Metrics Platform (MP) starting from schema creation (if applicable) by referencing the core interactions schemas, to implementing the relevant API methods for their use cases, onto verifying that events sent via MP are being submitted successfully and passing validation. ==== Requirements [] Architect solution [] Test cross platform requirements with an implementation draft

==== Background Coming out of a recent spike T345439 (Prototype API for Submitting Core Interaction Events), we have an initial proposal for an API that specifies some preliminary methods for submitting events against the newly drafted, to-be-merged [[ https://gerrit.wikimedia.org/r/c/schemas/event/secondary/+/952252 | core interactions schemas ]] (See T345439#9217684). ==== Developer notes Presumably this goal entails documenting the proposed API and detailing the process by which a given instrument managed by a feature team can use the Metrics Platform (MP) starting from: - schema creation (if applicable) by referencing the core interactions schemas - implementing the relevant API methods for their use cases in client code - adding new stream configs for the respective instrument (if a new custom concrete schema is being introduced) - verifying that events sent via MP are being submitted successfully and passing validation We should also document MP-owned schemas so that feature teams can easily reference them in their own custom schemas or use them directly. ==== Requirements [] Architect solution [] Test cross platform requirements with an implementation draft

==== Background Coming out of a recent spike T345439 (Prototype API for Submitting Core Interaction Events), we have an initial proposal for an API that specifies some preliminary methods for submitting events against the newly drafted, to-be-merged [[ https://gerrit.wikimedia.org/r/c/schemas/event/secondary/+/952252 | core interactions schemas ]] (See T345439#9217684). ==== Developer notes Presumably this goal entails documenting the proposed API and detailing the process by which a given instrument managed by a feature team can use the Metrics Platform (MP) starting from: - schema creation (if applicable) by referencing the core interactions schemas, to - implementing the relevant API methods for their use cases, onto in client code - adding new stream configs for the respective instrument (if a new custom concrete schema is being introduced) - verifying that events sent via MP are being submitted successfully and passing validation We should also document MP-owned schemas so that feature teams can easily reference them in their own custom schemas or use them directly. ==== Requirements [] Architect solution [] Test cross platform requirements with an implementation draft