Docs 19.07.15 release (Weeks 2 & 3, 2026)

docs/apps/services/ignored-services.mdx

@@ -3,29 +3,58 @@ title: "Ignored Services"
 sidebar_position: 6
 ---
 
-Select _Apps > Services > Ignored Services_ to view, edit, or add ignored services. Click the ignored service ID to edit an existing service.
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+Select **Apps > Services > Ignored Services** to view, edit, or add ignored services. Click the ignored service ID to edit an existing service.
 
 Ignored services are either Active or Inactive:
 
 - Active ignored services are not captured in discovery.
 - Inactive ignored services are captured in discovery.
 
-Any discovered ignored services are added to the Ignored Services page. You can edit an individual ignored service to change its ignored status or use the Action menu to edit multiple services. You can also add ignored services manually if you want.
+Any discovered ignored services are added to the **Ignored Services** list page. 
+
+<ThemedImage
+  alt="Ignored Services"
+  sources={{
+    light: useBaseUrl('/assets/images/services/ignored-services-list-page-light.png'),
+    dark: useBaseUrl('/assets/images/services/ignored-services-list-page-dark.png'),
+  }}
+/>
 
-![](/assets/images/WEB-293_Service-Ignored-View.png)
+You can edit an individual ignored service to change its ignored status or use the **Actions** menu to edit multiple services. 
 
-![](/assets/images/D42-15730_Ignored-Services-Edit.png)
+<ThemedImage
+  alt="Edit Ignored Service"
+  sources={{
+    light: useBaseUrl('/assets/images/services/edit-ignored-services-light.png'),
+    dark: useBaseUrl('/assets/images/services/edit-ignored-services-dark.png'),
+  }}
+/>
 
 ### Ignored Services Actions
 
 Select one or more ignored service, and then select an Action to apply to the ignored services. You can use the Action menu to activate or deactivate selected ignored services, and you can also delete or export ignored services.
 
-![](/assets/images/WEB-293_Service-Ignored-View-Action_Menu.png)
+<ThemedImage
+  alt="Ignored Services actions"
+  sources={{
+    light: useBaseUrl('/assets/images/services/ignored-services-actions-light.png'),
+    dark: useBaseUrl('/assets/images/services/ignored-services-actions-dark.png'),
+  }}
+/>
 
 ### Add an Ignored Service
 
-Click _Add Ignored Service_ to add an ignored service.
+Click **Create** from the Ignored Services list page to add an ignored service.
 
-Enter the **Ignored Text** and select the **Ignored Level**.  Click **Active** to add the ignored service as active – active ignored services are not captured in discovery. Click _Save_ to add the ignored service.
+Enter the **Ignored Text** and select the **Ignored Level**.  Click **Active** to add the ignored service as active – active ignored services are not captured in discovery. Click **Save** to add the ignored service.
 
-![](/assets/images/WEB-293_Service-Ignored-Add.png)
+<ThemedImage
+  alt="Create an Ignored Service"
+  sources={{
+    light: useBaseUrl('/assets/images/services/add-ignored-service-light.png'),
+    dark: useBaseUrl('/assets/images/services/add-ignored-service-dark.png'),
+  }}
+/>

docs/apps/services/index.mdx

@@ -1,26 +1,39 @@
 ---
-title: "Services"
+title: "All Services"
 sidebar_position: 1
 ---
 import ThemedImage from '@theme/ThemedImage';
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-The Services menu contains the items shown below.
-
-<ThemedImage
-  alt="Services menu options"
-  sources={{
-    light: useBaseUrl('/assets/images/services-menu-light.png'),
-    dark: useBaseUrl('/assets/images/services-menu-dark.png'),
-  }}
-/>
-
-When you create a discovery job, remember to select the Discover Services option to discover services information.
-
-<ThemedImage
-  alt="Software and Applications menu options"
-  sources={{
-    light: useBaseUrl('/assets/images/software-and-applications-options-light.png'),
-    dark: useBaseUrl('/assets/images/software-and-applications-options-dark.png'),
-  }}
-/>
+A Service is any communication process between a listener and client discovered via netstat in Device42.
+
+Use the **All Services** list page to see which services are running across your infrastructure and how many instances of each exist. View widely-deployed applications and noisy monitoring agents.
+
+- Navigate to **Resources > Services** to view and manage the discovered services.
+
+  <ThemedImage
+    alt="Services menu options"
+    sources={{
+      light: useBaseUrl('/assets/images/services/services-menu-light.png'),
+      dark: useBaseUrl('/assets/images/services/services-menu-dark.png'),
+    }}
+  />
+
+## Application Dependency Mapping and Services
+
+For [Application Dependency Mapping (ADM)](/apps/index.mdx), reviewing **All Services** and [**Service Instances**](service-instances.mdx) of the Device42 Main Appliance is particularly useful.
+
+### All Services vs Service Instances
+
+The All Services list page has records of the unique names of the discovered services and the number of **Service Instances** with that name. For example:
+
+- `15` instances of `java`
+- `8` instances of `java.exe`
+
+Identify noisy services, like agents, from the All Services list page by sorting the **Service Instances** column from high to low count.
+
+The Service Instances list page stores every discovered service as an individual entry, with the **Device** it's running on and [other details](service-instances.mdx). For example:
+
+- `java.exe` running on device `jboss-27`
+- `java.exe` running on device `jboss-29`
+

docs/apps/services/network-shares.mdx

@@ -11,8 +11,8 @@ Navigate to **Resources > Storage > Network Shares** of the main appliance to vi
 <ThemedImage
   alt="Network Shares list page"
   sources={{
-    light: useBaseUrl('/assets/images/network-shares/network-shares-list-page-light.png'),
-    dark: useBaseUrl('/assets/images/network-shares/network-shares-list-page-dark.png'),
+    light: useBaseUrl('/assets/images/services/network-shares-list-page-light.png'),
+    dark: useBaseUrl('/assets/images/services/network-shares-list-page-dark.png'),
   }}
 />
 
@@ -23,8 +23,8 @@ Select one or more network shares and choose an action from the **Select an acti
 <ThemedImage
   alt="Network Shares actions"
   sources={{
-    light: useBaseUrl('/assets/images/network-shares/network-shares-actions-light.png'),
-    dark: useBaseUrl('/assets/images/network-shares/network-shares-actions-dark.png'),
+    light: useBaseUrl('/assets/images/services/network-shares-actions-light.png'),
+    dark: useBaseUrl('/assets/images/services/network-shares-actions-dark.png'),
   }}
 />
 
@@ -39,7 +39,7 @@ Optionally, you can select an **Install Date** and fill in the **Caption**, **St
 <ThemedImage
   alt="Network Shares actions"
   sources={{
-    light: useBaseUrl('/assets/images/network-shares/add-network-share-light.png'),
-    dark: useBaseUrl('/assets/images/network-shares/add-network-share-dark.png'),
+    light: useBaseUrl('/assets/images/services/add-network-share-light.png'),
+    dark: useBaseUrl('/assets/images/services/add-network-share-dark.png'),
   }}
 />

docs/apps/services/scheduled-tasks.mdx

@@ -3,20 +3,41 @@ title: "Scheduled Tasks"
 sidebar_position: 3
 ---
 
-Select _Apps > Services > Scheduled Tasks_ to view, edit, or add a scheduled task.
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
 
-![](/assets/images/WEB-293_Scheduled-Task-View.png)
+Select **Resources > Services > Scheduled Tasks** to view, edit, or add a scheduled task.
+
+<ThemedImage
+  alt="Service Instance Actions menu"
+  sources={{
+    light: useBaseUrl('/assets/images/services/scheduled-tasks-light.png'),
+    dark: useBaseUrl('/assets/images/services/scheduled-tasks-dark.png'),
+  }}
+/>
 
 ### Scheduled Task Actions
 
 Select one of more scheduled tasks, and then select an Action to apply that action to the tasks.
 
-![](/assets/images/WEB-293_Scheduled-Task-View-Actions-Menu.png)
+<ThemedImage
+  alt="Service Instance Actions menu"
+  sources={{
+    light: useBaseUrl('/assets/images/services/scheduled-tasks-actions-light.png'),
+    dark: useBaseUrl('/assets/images/services/scheduled-tasks-actions-dark.png'),
+  }}
+/>
 
 ### Add a Scheduled Task
 
-Click _Add Scheduled Task_ to add a new task.
+Click **Create** from the Scheduled Tasks list page to add a new task.
 
-![](/assets/images/WEB-293_Scheduled-Task-Add.png)
+<ThemedImage
+  alt="Service Instance Actions menu"
+  sources={{
+    light: useBaseUrl('/assets/images/services/create-scheduled-task-light.png'),
+    dark: useBaseUrl('/assets/images/services/create-scheduled-task-dark.png'),
+  }}
+/>
 
-Enter a **Name**, **Caption**, and select a **Device** for the task. Enter or select any other options or schedule information. Click _Save_ at the bottom of the page to save the task.
+Enter a **Name**, **Caption**, and select a **Device** for the task. Enter or select any other options or schedule information. Click **Save** at the bottom of the page to save the task.

docs/apps/services/service-communications.mdx

@@ -3,33 +3,72 @@ title: "Service Communications"
 sidebar_position: 5
 ---
 
-Select Resources _> Services > Service Communications_ to view, edit, or add service communication information.  Click the _Client_ device name to edit an existing service communication.
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
 
-![](/assets/images/WEB-787_1.png)
+Select **Resources > Services > Service Communications** to view, edit, or add service communication information.  Click the **Client** device name to edit an existing service communication.
 
-![](/assets/images/WEB-787_2.png)
+<ThemedImage
+  alt="Service Communications list page"
+  sources={{
+    light: useBaseUrl('/assets/images/services/service-communications-list-page-light.png'),
+    dark: useBaseUrl('/assets/images/services/service-communications-list-page-dark.png'),
+  }}
+/>
 
 ### Service Communications Actions
 
-Select one or more Service Communications, and then select an Action to apply the action to the items.
+Select one or more Service Communication records, and then select an Action to apply the action to the items.
 
-![](/assets/images/WEB-787_3.png)
+<ThemedImage
+  alt="Service Communications actions"
+  sources={{
+    light: useBaseUrl('/assets/images/services/service-communications-actions-light.png'),
+    dark: useBaseUrl('/assets/images/services/service-communications-actions-dark.png'),
+  }}
+/>
 
 ### Add a Service Communication
 
-Click _Add Service Communication_ to add a new communication.
+Click **Create** from the Service Communications list page to add a new communication.
 
-![](/assets/images/WEB-787_4.png)
+<ThemedImage
+  alt="Create a Service Communication"
+  sources={{
+    light: useBaseUrl('/assets/images/services/add-service-communications-light.png'),
+    dark: useBaseUrl('/assets/images/services/add-service-communications-dark.png'),
+  }}
+/>
 
 Enter a Client IP Address, Listener IP Address. Port, and Protocol. You can also select the Client Device, Listener Device, and enter a Client process display name and a Client process name. Click Save at the bottom of the page to ad the service communication.
 
 ### Service Port IP Statistics
 
-Select _Apps > Services > Service Communications_ to view service port IP statistics. As of version 16.00.00, Device42 has revamped statistics collection. Statistics are now only kept from a listener perspective and are client-IP-centric (not per client service). Previously collected statistics now appear in the _Classic Statistics_ section of this page. See below for descriptions of the Netstat and Netflow statistics Device42 collects.
+Select **Resources > Services > Service Communications** and click on a record **ID** to view service port IP statistics. 
 
-![](/assets/images/WEB-787_5.png)
+Statistics are only kept from a listener perspective and are client-IP-centric (not per client service). Collected statistics appear in the **Classic Statistics** section of this page. See below for descriptions of the Netstat and Netflow statistics Device42 collects.
 
-#### Netstat Statistics
+**Statistics**
+
+<ThemedImage
+  alt="Service Communication Statistics"
+  sources={{
+    light: useBaseUrl('/assets/images/services/service-communications-statistics-light.png'),
+    dark: useBaseUrl('/assets/images/services/service-communications-statistics-dark.png'),
+  }}
+/>
+
+**Classic Statistics**
+
+<ThemedImage
+  alt="Service Communication Classic Statistics"
+  sources={{
+    light: useBaseUrl('/assets/images/services/classic-statistics-light.png'),
+    dark: useBaseUrl('/assets/images/services/classic-statistics-dark.png'),
+  }}
+/>
+
+### Netstat Statistics
 
 <table>
   <tbody>

docs/apps/services/service-instances.mdx

@@ -3,20 +3,82 @@ title: "Service Instances"
 sidebar_position: 2
 ---
 
-Select _Apps > Services > Service Instances_ to view, edit, or or add service instances.Click on a _Service Name_ to view or edit that instance.
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
 
-![](/assets/images/WEB-293_Service-Instance-View.png)
+Service Instances are the running services discovered on your devices. These form the foundation for Application Dependency Mapping and help you understand what's running where.
+
+Device42 stores each discovered service as an entry in the Service Instance list page, under **Resources > Service Instances**. You'll see multiple services with the same **Service Name**. If you want a tally of the number of services with the same name, visit the [All Services](/apps/services/index.mdx) list page under **Resources > All Services**.
+
+A Service Instance record includes the service **Device**, its **State**, **Service Path**, **Listener Addresses**, and **Ports**.
+
+## Using the Service Instances Interface
+
+From **Resources > Service Instances**, click on a **Service Name** to view or edit that instance.
+
+<ThemedImage
+  alt="Service Instance list page"
+  sources={{
+    light: useBaseUrl('/assets/images/services/service-instance-list-page-light.png'),
+    dark: useBaseUrl('/assets/images/services/service-instance-list-page-dark.png'),
+  }}
+/>
 
 ### Service Instances Actions
 
-Select one of more service instances, and then select an Action to apply that action to the instances.
+Select one or more Service Instances and select an option from the **Actions** menu to perform on the selection.
 
-![](/assets/images/WEB-293_Service-Instance-View-Actions-Menu.png)
+<ThemedImage
+  alt="Service Instance Actions menu"
+  sources={{
+    light: useBaseUrl('/assets/images/services/service-instances-actions-light.png'),
+    dark: useBaseUrl('/assets/images/services/service-instances-actions-dark.png'),
+  }}
+/>
 
 ### Add a Service Instance
 
-Click _Add Service Instance_ to add a new instance.
+Click **Create** to add a new instance.
+
+<ThemedImage
+  alt="Add Service Instance form"
+  sources={{
+    light: useBaseUrl('/assets/images/services/add-service-instance-light.png'),
+    dark: useBaseUrl('/assets/images/services/add-service-instance-dark.png'),
+  }}
+/>
+
+- Click **Service** to select the service you want to add. Device42 displays the Select Service dialog – you can also add a new component from this dialog. 
+- Select the **Start Mode**, **State**, and **Topology Status**. 
+
+Enter or select any other information you want for the instance, and then click **Save** at the bottom of the page.
+
+## Application Dependency Mapping and Service Instances
+
+As part of the [Application Dependency Mapping (ADM) workflow](/apps/enterprise-application-dependency-mapping/index.mdx), Device42 creates Application Components (**Applications > Application Components**) from discovered data and services. Application Components are building blocks for creating Application Groups, and eventually, a Business Service. 
+
+If you have an application that is absent or not quite captured as an Application Component, after running OS-level discovery jobs with ADM sampling enabled, create an Application Component Template to instruct Device42 on what to look for.
+
+The **Service Command Args** value of a Service Instance can be used as match criteria when configuring the Application Component Template you need. 
+
+- Copy the **Service Command Args** value of a Service Instance. 
+
+<ThemedImage
+  alt="Service Instance Example"
+  sources={{
+    light: useBaseUrl('/assets/images/services/service-instances-args-example-light.png'),
+    dark: useBaseUrl('/assets/images/services/service-instances-args-example-dark.png'),
+  }}
+/>
+
+- Create a new Application Component Template using the previous Service Instance **Service Command Args** value as match criteria:
 
-![](/assets/images/WEB-293_Service-Instance-Add.png)
+<ThemedImage
+  alt="Application Component Template"
+  sources={{
+    light: useBaseUrl('/assets/images/services/app-comp-template-arg-light.png'),
+    dark: useBaseUrl('/assets/images/services/app-comp-template-arg-dark.png'),
+  }}
+/>
 
-Click **Service** to select the service you want to add. Device42 displays the Select Service dialog – you can also add a new component from this dialog. Click on the name of the service you want to add. Select the **Start Mode**, **State**, and **Topology Status**. Enter or select any other information you want for the instance, and then click _Save_ at the bottom of the page.
+Creating Application Component Templates for Java.exe applications is particularly useful - you provide the command line switches (**Service Command Args**) containing the launch details of the service.