#waffle434 1/5 🟩🟩🟩🟩🟩 🟩⬜🟩⬜🟩 🟩🟩⭐🟩🟩 🟩⬜🟩⬜🟩 🟩🟩🟩🟩🟩 πŸ”₯ streak: 27 πŸ₯ˆ #wafflesilverteam https://t.co/4doM5G9lQM

#waffle434 1/5 🟩🟩🟩🟩🟩 🟩⬜🟩⬜🟩 🟩🟩⭐🟩🟩 🟩⬜🟩⬜🟩 🟩🟩🟩🟩🟩 πŸ”₯ streak: 27 πŸ₯ˆ #wafflesilverteam https://t.co/4doM5G9lQM — Warren Myers 🐧🐿 (@warrenmyers) Mar 31, 2023 from Twitter https://twitter.com/warrenmyers March 30, 2023 at 09:01PM via IFTTT

@michaeldf88 🌎 Mar 30, 2023 🌍 πŸ”₯ 26 | Avg. Guesses: 6.09 🟨🟧🟨πŸŸ₯πŸŸ₯🟩 = 6 https://t.co/D1t41eb7bA #globle

@michaeldf88 🌎 Mar 30, 2023 🌍 πŸ”₯ 26 | Avg. Guesses: 6.09 🟨🟧🟨πŸŸ₯πŸŸ₯🟩 = 6 https://t.co/D1t41eb7bA #globle — Warren Myers 🐧🐿 (@warrenmyers) Mar 30, 2023 from Twitter https://twitter.com/warrenmyers March 30, 2023 at 11:28AM via IFTTT

Favorite tweets

🌎 Mar 30, 2023 🌍 πŸ”₯ 1 | Avg. Guesses: 5.27 πŸŸ₯πŸŸ₯πŸŸ₯πŸŸ₯🟩 = 5 https://t.co/bcsxw4E8Gj #globle @warrenmyers — CatsFanInOhio πŸ‡ΊπŸ‡¦ (@michaeldf88) Mar 30, 2023 from http://twitter.com/michaeldf88 via IFTTT

Answer by warren for Assigning a subsearch result to a variable

I would probably do this as separate searches on the dashboard, unless there was an overwhelming need to have it all in one Alternatively, you could | append each search, & | stats values at the ed like this: index=ndx sourcetype=srctp "middleware 1" "domain1.tld" userid=* | stats dc(userid) as domain1users | append [| search index=ndx …
Continue reading Answer by warren for Assigning a subsearch result to a variable

Favorite tweets

‘Hole’ in the sun unleashes powerful X1.2 solar flare, threatens space weather mayhem https://t.co/7Q1gJUl2kv https://t.co/w5sy77UxNp — SPACE.com (@SPACEdotcom) Mar 30, 2023 from http://twitter.com/SPACEdotcom via IFTTT

Favorite tweets

Remember when I said on the show in 2020 the virus itself was merely the MacGuffin for the real the bio-weapon? The psy ops that followed it? https://t.co/u0cJkV0ZXD — Steve Deace (@SteveDeaceShow) Mar 30, 2023 from http://twitter.com/SteveDeaceShow via IFTTT