Merge pull request #496 from ritza-co/19.07.17

Docs 19.07.17 release (Week 6, 2026)

Author: sixhobbits

docs/getstarted/deploy-device42/sizing-recommendations.mdx

@@ -3,19 +3,32 @@ title: "Sizing Recommendations"
 sidebar_position: 4
 ---
 
-Use the sizing recommendations below to properly provision your Device42 Main Appliance, Remote Collectors, and Windows Discovery Service. 
+Use the sizing recommendations below to properly provision your Device42 Main Appliance, Remote Collectors (RC), and Windows Discovery Service (WDS). 
 
-The sizing requirements depend on the size of the environment and the Device42 features used.
+Sizing requirements depend on the size of your environment and the Device42 features you use.
 
 | Device42 Item                                    | Sizing and Notes |
 |--------------------------------------------------|------------------|
 | One Main Appliance (virtual appliance) | **Small to medium environments (\<2500 devices):**  <br/> - Four vCPU <br/> - 16GB RAM <br/> - 150GB vDisk (SSD or flash disk recommended)<br/><br/>  **Medium to large environments (>2500 devices):** <br/>- 16 vCPU <br/>- 64GB RAM <br/>- 150GB vDisk (SSD or flash disk recommended)<br/><br/>  For any environments that include Application Dependency Mapping (ADM), Resource Utilization (RU), or Storage discovery, follow the medium to large environment guidelines |
 | Remote Collector(s) (virtual appliance) | **One RC per 1000 workloads:** <br/>- Two vCPU <br/>- 4GB RAM <br/>- 50GB vDisk |
 | Windows Discovery Service (.NET installer) | **One WDS per 1000 workloads:**  <br/> - Two vCPU <br/> - 8GB RAM <br/> - 50GB vDisk (minimum) |
 
-Depending on your environment, we may recommend a dedicated resource pool for the virtual appliance to ensure there is no resource contention. 
+## Recommendations
 
-Device42 utilizes a database within the virtual appliance we recommend solid-state storage, or similar storage optimized for database operations.
+The following are general recommendations, but the optimal setup depends on your specific infrastructure. [Contact support](https://support.device42.com/hc/en-us) for more guidance.
 
-For Windows infrastructure, Device42 requires a WDS to be installed on one machine per discovery
-segment/Remote Collector.
+### RC for Large Workloads
+
+First, increase the CPU and RAM when adding more workloads (> 1000) to the Remote Collector. If the Remote Collector is still performing slowly, add more Remote Collectors.
+
+### Dedicated Resource Pool
+
+Depending on your environment, a dedicated resource pool for the virtual appliance may be necessary to ensure there is no resource contention.
+
+### Database Storage
+
+Device42 uses a database within the virtual appliance. Solid-state storage, or similar storage optimized for database operations is recommended.
+
+### WDS Installation
+
+For Windows infrastructure, Device42 requires a WDS to be installed on one machine per discovery segment or Remote Collector.

docs/integration/external-integrations/freshservice-integration/index.mdx

@@ -14,24 +14,22 @@ This page covers the initial setup and installation of the Freshservice integrat
 
 ## About the Device42 Freshservice Integration
 
-*Seamless ITSM and CMDB integration.*
-
 ![Device42 Freshservice logos](/assets/images/freshservice-integration/device42-freshservice-logos.png)
 
-Device42 integrates with Freshservice to provide the following capabilities: 
+Device42 integrates with Freshservice for seamless ITSM and CMDB integration, providing the following capabilities:
 
 - Enhanced ITSM workflows with detailed device, user, and software information.
 - An understanding of how changes to a particular application or network port could affect your business services. 
 - Flexible CMDB import options that ensure the right data is brought into the right place.
 - A single login page for accessing both Device42 and Freshservice. 
 
-    <ThemedImage
-    alt="Freshworks login button"
-    sources={{
-        light: useBaseUrl('/assets/images/freshservice-integration/freshworks-login-button-light.png'),
-        dark: useBaseUrl('/assets/images/freshservice-integration/freshworks-login-button-dark.png'),
-    }}
-    />
+<ThemedImage
+alt="Freshworks login button"
+sources={{
+    light: useBaseUrl('/assets/images/freshservice-integration/freshworks-login-button-light.png'),
+    dark: useBaseUrl('/assets/images/freshservice-integration/freshworks-login-button-dark.png'),
+}}
+/>
 
 ## Install the Device42 Integration App on Freshservice
 
@@ -42,7 +40,7 @@ The installation process has three steps, which are discussed in more detail in
 Ensure that cloud services are enabled and configured:
 
 1. Navigate to **Tools > Integrations > Cloud Services**.
-2. Enter your externally accessible Device42 IP address or FQDN in the **D42 URL for SaaS apps** field. If you have configured a digital certificate, you can enter the name of the device instead. 
+2. Enter your Device42 IP address or FQDN in the **D42 URL for SaaS apps** field.
 3. Select your **Cloud Connector** location or environment. It's set to **USA** by default.
 
     <ThemedImage