Long running Discovery Schedules

Harish18
Kilo Contributor

‎05-07-2018 08:24 AM

We recently upgraded from Istanbul to Kingston version, the issue is with the Discovery Schedules. It is taking more time to complete when compared to our previous version. Can someone help me in knowing what makes it to run such long time when compared it to Istanbul version.

Labels:
0 Helpfuls
  • 1,650 Views
3 REPLIES 3

tim_broberg
ServiceNow Employee
ServiceNow Employee

‎05-07-2018 08:58 AM

Well, first, let's identify the slow probes.

Go to the Discovery Status of a completed slow discovery, click on the ecc queue tab, and sort on "created" from newest to oldest.

I bet you see a few probes that finish a lot later than the crowd.

What are the names of those probes?

0 Helpfuls

Harish18
Kilo Contributor
In response to tim_broberg

‎05-17-2018 07:08 AM

Hey Sorry for late reply, it's SNMP probe taking more than 1hour.

0 Helpfuls

tim_broberg
ServiceNow Employee
ServiceNow Employee
In response to Harish18

‎05-17-2018 01:09 PM

Oh, yeah. SNMP is definitely touchy by nature.

Knobs to consider fiddling with include:

  1. turning off probes you don't need, e.g. snmp - routing probes, which bring in huge results whose contents you may not care about
  2. tuning the timeout parameter
  3. use_getbulk (for tables)
  4. use_getscalar (for scalars)
  5. generally squinting at packet captures and trying to figure out where the time is going

I'm afraid I still need help every time I hit one of these issues with SNMP.

You might want to open an incident if you can't sort it out yourself within an hour or two.

I'm afraid empathy is most of what I can offer there. Let us know what you figure out?

    - Tim.