Today, when the customer routes to Discovery Schedule Creation, especially for Cloud, then they land up in the custom UI which guides in a step-by-step manner starting from Account Validation to Schedule creation i.e.,
Acconut Validation => Sub Account Discovery (Conditional) => Datacenter Discovery => Choice for IP Discovery => Schedule Frequency => Finish / Finish and Run
When things don't work as expected then logs play a crucial role in providing the information necessary for investigation of the issue and thereby landing up to the root cause eventually.
There are multiple ways to find the log information but some of the most useful ones are listed below.
- Discovery Logs – a tab present below along with Devices & ECC Queues when you open a Discovery Status record
- Pattern Execution Flow – You’ll get the option in Discovery Log itself for the specific pattern(s)
- MID Logs – User can check the /agent/logs/ folder wherever MID server is deployed (OR) Grab MID Logs option available in the MID Server Page in any SN Instance
- On-Demand Pattern Debug – If at all the above options aren’t helping then the user can create Cloud Service Account manually and Debug the respective pattern i.e., either Account Validation / Sub Account Discovery / Datacenter Discovery. This way user can run on-demand specific/individual steps execution to observe the data flow.
- System Logs – Provides the stack trace information, if at all any issue encountered during the discovery run.
- Cloud API Trail – During the Cloud Discovery Schedule run, the flow goes through CAPI ("Cloud API") along with the Patterns so in that case, the information related to CAPI exists in "Cloud API Trail" which can be found via Search in the left-side navigator of the instance homepage.
Please note, the Cloud API Trail doesn't contain any response(s) or information or log(s) related to the Patterns.
