@@WorstPractices No you actually ask them to do. But most of their intros do not actually help some other interesting topics like what their accomplishments are and what they are known for. Because I don't know any of these speakers so I had to google their names even after their intro. Thanks for the great videos.
Gotcha - maybe I could put even more information in the description. Would that work? I'm trying to keep the video super short and I worry about spending half the time on prologues.
So how do you use these rich events? Is this something you have to be a developer to do? Does this have more to do with turning up the verbosity of the logs when troubleshooting? Or just keeping a short log and notifying when something interesting happens. You tell us about the worst practice, but you don't really go into much detail about what you do instead.
He's suggesting "structured logging" with a predefined data schema as opposed to unstructured logging that is freeform text that is later translated into structured information. Some info on this approach is here: cloud.google.com/logging/docs/structured-logging
Thanks for sharing these videos. They are very relatable. Would you mind giving an intro of the speaker in the future videos? Thanks again
I had asked the person to introduce themselves in the beginning. Could you let me know what else you'd like to know? Thanks!
@@WorstPractices No you actually ask them to do. But most of their intros do not actually help some other interesting topics like what their accomplishments are and what they are known for. Because I don't know any of these speakers so I had to google their names even after their intro. Thanks for the great videos.
Gotcha - maybe I could put even more information in the description. Would that work? I'm trying to keep the video super short and I worry about spending half the time on prologues.
@@WorstPractices That works perfectly.
So how do you use these rich events? Is this something you have to be a developer to do? Does this have more to do with turning up the verbosity of the logs when troubleshooting? Or just keeping a short log and notifying when something interesting happens.
You tell us about the worst practice, but you don't really go into much detail about what you do instead.
He's suggesting "structured logging" with a predefined data schema as opposed to unstructured logging that is freeform text that is later translated into structured information. Some info on this approach is here: cloud.google.com/logging/docs/structured-logging