Telemetry schemas#141
Conversation
geekingfrog
left a comment
geekingfrog
left a comment
There was a problem hiding this comment.
In general, I don't know where any of these requirements came from.
Like, what things are we trying to know? What features do we want?
The whole thing about anonHash doesn't make sense, there is no concept of unauthenticated tachyon connection, at least yet. If we allow that, that would need additional considerations and discussion.
That read like some hallucination without much thought behind.
| contents: Type.String({ | ||
| description: "Base64-encoded, gzip-compressed log contents.", | ||
| }), |
There was a problem hiding this comment.
that's not going to fly. Tachyon (and anything json based in general) is absolutely not meant to move files around. This can be big as well, making it really really not a good fit for that kind of thing.
There was a problem hiding this comment.
what is this about? it says "set or overwrite", how do you retrieve it? I don't get how you do any of that.
There was a problem hiding this comment.
I don't think we need a different message between simple and complex. The payload can be optional, and that's it.
|
Overall, it needs to be discussed. I based it solely on the task and simply wanted to approach the discussion with anything, with any vision. The discussion is open |
2 participants
Closed #140
Adds four new Tachyon endpoints under the telemetry/ namespace to support client-side analytics in bar-lobby:
telemetry/simpleClientEvent- log a named event with no payloadtelemetry/complexClientEvent- log a named event with an arbitrary JSON payload (max 4096 bytes)telemetry/updateClientProperty- set or overwrite a named client property (e.g. window mode, resolution)telemetry/uploadInfolog- upload a gzip-compressed, base64-encoded log file; responds with infoLogId