Docker discovery isn't working. Issue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Symptoms Docker discovery is not working. Release J and above. Cause This could happen if the Docker pattern wasn't triggered at all. Check that the pattern has been triggered. For the docker pattern to be triggered, the horizontal pattern probe should be launched which in turn triggers the Docker pattern. This happens if the docker process is first detected by the classifiers for docker engine. Resolution On the list of the process classifications for Discovery, for the Docker Engine process (cmdb_ci_docker_engine table), check that the enlisted conditions' values match with the values returned on the discovery payload. Usually, the conditions on the classifier have values like 'Name', 'dockerd' and 'docker-daemon'. Check that the discovery payload also contains these values. If this is not the case, modify the condition on the process classifier for the docker engine and add an 'OR' condition to check for the following- 'Parameters' contains 'docker'. Save this change on the classifier and run a new discovery scan. This should trigger the docker pattern.