# ServiceNow Search CI help

**URL:** <https://discuss.rapid7.com/t/servicenow-search-ci-help/2091>\
**Category:** Plugins\
**Tags:** InsightConnect, servicenow\
**Created:** [October 9, 2020, 1:56am UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091 "2020-10-09T01:56:06Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon\_mcclure](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/brandon_mcclure/32/182_2.png) [@brandon\_mcclure](https://discuss.rapid7.com/u/brandon_mcclure)\
**Post date:** [October 9, 2020, 1:56am UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/1 "2020-10-09T01:56:06Z")

</div>

I’m having some trouble with searching for a CI using the rapid7/servicenow:4.1.0 plugin and “Search CI” Action.  
Using cURL I can do a query fqdnLIKEserver01&name=server01 to look for a server but not the vmware instances of it, but when I do this in InsightConnect it ignores the second part. I’ve tried

- fqdnLIKEserver01^ANDname=server01
- fqdnLIKEserver01ANDname=server01
- fqdnLIKEserver01,name=server01

and they either give me the same thing or nothing at all. what am I doing wrong?

---

<div class="post-metadata">

**Author:** ![holly\_wilsey](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/holly_wilsey/32/78_2.png) [@holly\_wilsey](https://discuss.rapid7.com/u/holly_wilsey)\
**Post date:** [October 14, 2020, 3:38pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/2 "2020-10-14T15:38:51Z")

</div>

Have you tried something like `fqdnLIKEserver01^name=server01` ? (I removed the AND there)

I know some of their operators can be funky or inconsistent. Like I think they use `^OR` for “or” but just `^` for “and.”

---

<div class="post-metadata">

**Author:** ![brandon\_mcclure](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/brandon_mcclure/32/182_2.png) [@brandon\_mcclure](https://discuss.rapid7.com/u/brandon_mcclure)\
**Post date:** [October 14, 2020, 3:54pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/3 "2020-10-14T15:54:27Z")

</div>

You are Awesome! Exactly what I was looking for!

---

<div class="post-metadata">

**Author:** ![holly\_wilsey](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/holly_wilsey/32/78_2.png) [@holly\_wilsey](https://discuss.rapid7.com/u/holly_wilsey)\
**Post date:** [October 14, 2020, 3:58pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/4 "2020-10-14T15:58:49Z")

</div>

Yay, glad it worked!

I had to do some digging for it, but I finally found a guide for their operators:

[https://docs.servicenow.com/bundle/paris-platform-user-interface/page/use/common-ui-elements/reference/r\_OpAvailableFiltersQueries.html](https://docs.servicenow.com/bundle/paris-platform-user-interface/page/use/common-ui-elements/reference/r_OpAvailableFiltersQueries.html)

---

<div class="post-metadata">

**Author:** ![brandon\_mcclure](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/brandon_mcclure/32/182_2.png) [@brandon\_mcclure](https://discuss.rapid7.com/u/brandon_mcclure)\
**Post date:** [October 14, 2020, 4:00pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/5 "2020-10-14T16:00:24Z")

</div>

My googlefu is failing me ☹ thank you, I have bookmarked that site

---

<div class="post-metadata">

**Author:** ![brandon\_mcclure](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/brandon_mcclure/32/182_2.png) [@brandon\_mcclure](https://discuss.rapid7.com/u/brandon_mcclure)\
**Post date:** [October 20, 2020, 8:10pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/6 "2020-10-20T20:10:20Z")

</div>

I see now that the plugin is populating the sysparm\_query parameter and that is what was throwing me off.  
Would it be possible to get some of the other parameters also like sysparm\_fields, sysparm\_limit, or sysparm\_offset?  
I’ve noticed the memory usage of my container is growing pretty fast and since I only need a field or two from my checks I’d think limiting the data returned to those would save me from having to constantly bounce the container and also speed up Jobs.

---

<div class="post-metadata">

**Author:** ![holly\_wilsey](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/holly_wilsey/32/78_2.png) [@holly\_wilsey](https://discuss.rapid7.com/u/holly_wilsey)\
**Post date:** [October 22, 2020, 8:44pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/7 "2020-10-22T20:44:24Z")

</div>

I looked into the Search action a little more and you raise a good point. My understanding is that sysparm\_fields is used to specify the fields being returned, and sysparm\_limit and sysparm\_offset are used for limiting the number of results and allowing for paging, respectively. I’m going to submit a request for this so we can take a look, since I think it’s a valid issue.

---

<div class="post-metadata">

**Author:** ![brandon\_mcclure](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/brandon_mcclure/32/182_2.png) [@brandon\_mcclure](https://discuss.rapid7.com/u/brandon_mcclure)\
**Post date:** [October 22, 2020, 9:14pm UTC](https://discuss.rapid7.com/t/servicenow-search-ci-help/2091/8 "2020-10-22T21:14:50Z")

</div>

Exactly what I was looking for.  
sysparm\_fields is what I’m looking for because I am only interested in returning 3 fields, but I could see other cases where you would want to limit the returned numbers and offset it to page through them to decrease load.

Also, if this becomes a cloud plugin (I think it would be a good candidate for it) I’m sure the decreased load would be appreciated.
