# Testing only spicy analyzers **URL:** \ **Category:** Zeek\ **Created:** [December 21, 2021, 8:43am UTC](https://community.zeek.org/t/testing-only-spicy-analyzers/6434 "2021-12-21T08:43:09Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![clopmz](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@clopmz](https://community.zeek.org/u/clopmz)\ **Post date:** [December 21, 2021, 8:43am UTC](https://community.zeek.org/t/testing-only-spicy-analyzers/6434/1 "2021-12-21T08:43:09Z")
Good morning, Maybe this is a stupid question, but is it possible to test only spicy analyzers in a standalone zeek installation? I would like to test these analyzers before to deploy them in our zeek cluster and use a Zeek standalone instance with minimal default Zeek analyzers. Regards. ---
**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\ **Post date:** [December 22, 2021, 10:04am UTC](https://community.zeek.org/t/testing-only-spicy-analyzers/6434/2 "2021-12-22T10:04:12Z")
Hmm, not easily I think. Two ideas: - You could run in bare mode ("-b"), that then won’t pull in any default scripts and hence effectively disable the default analyzers. However, it disables everything else as well, so you’d need to pick and choose which scripts you want. - You can turn off individual analyzers from inside zeek\_init(), but would need to iterate through them all. Example for disabling an analyzer here: [https://github.com/zeek/spicy-analyzers#configuration](https://github.com/zeek/spicy-analyzers#configuration) (that’s for disabling a Spicy analyzer, but works the same for default ones) Robin ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:47pm UTC](https://community.zeek.org/t/testing-only-spicy-analyzers/6434/3 "2022-05-06T15:47:49Z")