Caelrith

LogLens just got it's own VScode extension, automatically highlights key fields in your log files, and allows for easy filtering using natural language, install it for free : marketplace.visualstudio.com/items?itemName… #debuggingcode #vscode #logging #json

LogLens now has a playground! Paste your JSON, Logfmt or nginx logs and use intuitive language to query them! Check it out : getloglens.com/playground #devops #rustlang #wasm #debugging #logs #nginx #debuggingcode

I got tired of grep and jq choking on massive log files, so I built a structured log viewer in Rust. 🦀 It parses JSON/Logfmt automatically and filters at read-speed. Today, I'm open sourcing the core engine. Check the code: github.com/Caelrith/logle… #rustlang #devops #cli

DataDash gives you a live feed of your logs pouring in with clear visuals, all from the terminal. learn more : datadash.dev

Want to supercharge the time you need to debug a live 500 error? check out the blog : datadash.dev/blog/posts/002…

@Shay_Slay_ I followed you! I'm making useful CLI tools for developers!

If you: • Code • Design • Build • Learn AI • Or just love tech Connect🤝 let’s grow together!

@s_chiriac getloglens.com, it's a very easy to use CLI tool for log analysis with much more natural syntax than other tools. If you're a developer working on big systems with lots of logs, you'll love it!

💸 I want to support your startup! I'll buy your service. Explain why and share your link in the comments.

@honour_can_code getloglens.com, an easy to use CLI log analysis tool to reduce your headache while debugging nasty little bugs!

drop your startup idea and someone would rate it and say the bitter truth.

@0xjesstech Yes that's a very good resource. Learned a lot there. However, I felt like a lot of 'plumbing' tools for devs were missing. Tried to fill the hole a bit by making this set of tools : blocktools.dev

I’ve been working in web3 for 5 years and this is the fastest way to get into it Whether you want to be in marketing, content, dev, security, BD, product, start with this course (it’s free) For non technical roles, this could be enough, for technical roles, pick a career track on Updraft and carry on learning (they’re all free)

@DavidsonLeparie JSON is love, JSON is life. sometimes pretty tricky to work with, especially nested fields. Learn how I mastered the art of debugging here : getloglens.com/blog/posts/005

We don’t get fancy UI screenshots. We get logs. Our art is in JSON.

Being a backend dev is 90% invisible work and 10% explaining why the frontend isn’t loading.

@rajafaaiz127 @immunefi congratz man! smart contract can be very tricky. if you need a quick sanity check next time, use sol-sentry straight from the command line : blocktools.dev

🟡 First Audit on immunefi 🟡 First bug confirmed @immunefi #immunefitribe immunefi.com/s/ss/?severity…

Want an easy way to visualize your JSONL files straight from the command line in a modern way? check out datadash.dev

@cvetanovv0 it's just getting started. the market is projected to grow at 18.7% CAGR, and expected to reach 7B USD in total valuation by 2033. Use sol-sentry for free to get a quick sanity check for your contracts : blocktools.dev

For anyone wondering if it's too late to get started with Web3 security. No, it's not too late!

@gusniawan You're right, although you don't want to end up with a bug you can't solve because of sparse logging. Logging to big SaaS is expensive, here's a blog post explaining how you can keep costs under control when debugging the most tenacious bugs : getloglens.com/blog/posts/007

Logging everything kills performance. Here's why: 👇 - CPU and memory cost: Formatting strings, serializing objects, and dumping stack traces consume CPU and memory. - I/O overhead: When you log every request, you make the I/O system busy. Disk and file operations are slow. - Network latency (for decentralized logging): Every tiny event will cost HTTP or TCP calls. Best practices: 👇 - Log only important events (ERROR, WARN, INFO). - Use DEBUG/TRACE levels only in development. - Batch or buffer log writes. - Don't log inside loops or high-frequency code paths.

@aayushmayush @CyfrinUpdraft I think sol-console might help you : blocktools.dev

Day 97 of learning #blockchain from @CyfrinUpdraft Wrote test for rebase token in foundry advanced Checked deposit, burn and did some basic integration tests Explored Diamond architecture pattern based repo named Compose Thinking of starting open source contribution asap

@leo_web3_ @CyfrinUpdraft looks great! Check out these tools, they will make your life easier ;) they sure did mine! blocktools.dev

🧠 Day 1 of learning #Web3 & #Blockchain Started the free @CyfrinUpdraft course to go back to basics. ✅ Learned about blockchain’s history ✅ Decentralization benefits, ✅ The Oracle Problem and Smart Contracts. ✅ Sent my first tx on Sepolia using MetaMask ⚡️ #Solidity

Our new log analysis' TUI in action. Like the syntax? try it out for free at getloglens.com

Stop overpaying for log SaaS! 💸 LogLens Pro helps slash cloud logging costs up to 99% by analyzing archived logs (even .gz) locally. See how faster debugging + lower costs deliver massive ROI for dev teams. Breakdown in our latest post: getloglens.com/blog/posts/007 #LogAnalysis

Really looking for feedback from the dev community on this.What's the most frustrating part of your current pre-deployment workflow? Trying to make sure Blocktools solves the right problems.

Just launched Blocktools, my new suite of Rust-based CLI tools for EVM devs. The main discussion is happening on Reddit now—come join and share your honest feedback! #web3dev #solidity #ethereum #rustlang reddit.com/r/ethdev/comme… blocktools.dev