How eventtracing/dawn works
Project type and purpose
• This is a multi‐platform SDK suite and management platform (“曙光埋点 Dawn”) for full‐link event tracing.
• It provides lightweight client SDKs for iOS, Android and H5, plus a server‐side application (easyinsight-server) and a web portal (easyinsight-front) for event definition, validation, storage and analysis.
File structure
• At the root you have a container repo (this project) using Git submodules under Sources/ for each sub‐project:
• Android/EventTracing-Android
• iOS/EventTracing-iOS plus debug & log‐viewer submodules
• H5/EventTracing-web
• easyinsight/easyinsight-server
• easyinsight/easyinsight-front
• No standalone frontend/backend directories at root; everything lives under Sources/….
• Configuration files (.gitignore, .gitmodules, LICENSE, CODE_OF_CONDUCT) indicate a mono‐repo orchestrating several independent deliverables.
README for additional insights
• Names key features: auto instrumentation, VTree object model, link tracking.
• Lists deliverables: iOS SDK, Android SDK, H5 SDK, easyinsight-server, easyinsight-front.
Key elements to capture
• Git submodule “Sources/…” structure as the build/deployment starting point
• Each SDK’s internal layering: instrumentation → VTree → output channel
• easyinsight-server’s roles: schema management, ingestion API, storage adapter
• easyinsight-front’s roles: virtual tree editor, object management, real‐time validation dashboard
• Data flows: app user actions → SDK events → server → DB → UI