This is pretty cool. I am in the process of setting up the observability platform for my company and wish id seen this before we decided on loki. But maybe in the future we might experience to moving to Parseable.
7:25 I actually like hard-coding stuff like this. That is viable in my case (services with single-digit number of instances) and it forces every config change to go through the same review and release process as the rest of the code, even if somewhat expedited.
Tried this, performant but really needs some basic sane helper methods. Blows my mind there isn't even a simple basic rust client to use with default rust logs
it's actually Vimium, a Chrome extension that adds vim-like keybindings to Chrome! Discovered it a few months ago and now I swear by it chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb
Amazing video as usual! You're doing a great job sharing about new Rust tools! Do you think you can share how you use Building a Second Brain in your workflow? how do you collect information and use it in videos.
Sounds interesting, tho it would be really interesting to see parseable's Open telemetry instrumentation so that sending logs to already existing applications is just a matter of switching the telemetry instrumentation. Do you know if they support that kind of thing? Also, what if the data coming to parseable has multiple schemas? Realistically in a big app you will include tons of different fields depending on the purpose of the log.
![Twenty One Pilots - “The Line” (from Arcane Season 2) [Official Music Video]](http://i.ytimg.com/vi/E2Rj2gQAyPA/mqdefault.jpg)
This is pretty cool. I am in the process of setting up the observability platform for my company and wish id seen this before we decided on loki. But maybe in the future we might experience to moving to Parseable.
nice, definitely report back on how it goes if you decide to go that route. I'm excited to integrate it into my own projects
7:25 I actually like hard-coding stuff like this. That is viable in my case (services with single-digit number of instances) and it forces every config change to go through the same review and release process as the rest of the code, even if somewhat expedited.
Tried this, performant but really needs some basic sane helper methods. Blows my mind there isn't even a simple basic rust client to use with default rust logs
What is that search window you use at 4:57?
it's actually Vimium, a Chrome extension that adds vim-like keybindings to Chrome! Discovered it a few months ago and now I swear by it chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb
1. analyze this to include in the dataset. 2. Train. 3. Implement. 😊 happy
Amazing video as usual! You're doing a great job sharing about new Rust tools!
Do you think you can share how you use Building a Second Brain in your workflow? how do you collect information and use it in videos.
Sounds interesting, tho it would be really interesting to see parseable's Open telemetry instrumentation so that sending logs to already existing applications is just a matter of switching the telemetry instrumentation. Do you know if they support that kind of thing? Also, what if the data coming to parseable has multiple schemas? Realistically in a big app you will include tons of different fields depending on the purpose of the log.
Parseable supports multiple schemas
Did anybody check out the AWS creds?
90% sure that I rotated them 🙃
👍