Traffic Based Service Mapping data validation

SupriyaR4553017
Giga Contributor

I am validating the data for the service mapping but keep getting same error message on running the discovery on one of the applications. I have validated patterns and creds but no issue found. Any suggestions?

2 REPLIES 2

Matthew_13
Kilo Sage

Lets see; 

The most likely causes when Service Mapping discovery keeps failing with the same error despite valid patterns and credentials:

  • Wrong MID Server used at runtime → force a known-good MID

  • Security/OS blocking commands (EDR, sudo, SELinux, PowerShell)

  • Unstable process or port (containers, ephemeral ports)

  • Same pattern step failing each run → ccheck Service Mapping error details and MID agent.log

If the error repeats exactly, it’s almost never credentials or the pattern itself.

Mid servers seems fine, checked MID agent.log file also but the errors are acceptable as per google so no luck there. Relevant ports also open. But same errors are coming. entry points are being discovered but the service component s are not discoverable. And if run quick discovery against those IPs, i can those CI's are identified and classified so no idea where is the gap.