Merge branch 'main' into 1146-installation

Author: Nadia-JSch

docs/apps/business-services/building-business-services-in-device42.mdx

@@ -116,7 +116,7 @@ Applications Groups are enabled by default in Device42, but you can disable the
     />
 
 
-### (Legacy) Pinning, Starring, and Hiding Services
+### For versions prior to 19.05: Pinning, Starring, and Hiding Services
 
 Now that we have enabled Application Groups, we must identify which services we want to Pin, Star, and Hide to continue to build out our Application Groups.  
 
@@ -172,7 +172,7 @@ Hovering over the timeline above the view will allow you to identify changes to
 
 ![](/assets/images/WEB-519_bus-apps-13-Affinity-Group-Chart-Timeline.png)
 
-### (Legacy) Refactoring Application Groups
+### For versions prior to 19.05: Refactoring Application Groups
 
 - There are times when choosing a different query to generate your Application Groups may be better suited for your environment. Navigate to **Tools > Integrations > Saved DOQL Queries**.
 

docs/auto-discovery/cloud-auto-discovery/google-cloud-platform-autodiscovery.mdx

@@ -6,6 +6,8 @@ sidebar_position: 4
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
+Use Device42's Google Cloud Platform (GCP) autodiscovery to automatically inventory your GCP infrastructure, including virtual machines, Kubernetes clusters, databases, networks, and load balancers.
+
 ## Google Cloud Platform Discovery Items
 
 The following table outlines the Google Cloud Platform (GCP) items that Device42 automatically discovers, the types of information generated for each item, and where that information can be found in Device42.
@@ -18,6 +20,41 @@ The following table outlines the Google Cloud Platform (GCP) items that Device42
 | SQL DB                      |                              | [SQL Admin API](https://www.googleapis.com/discovery/v1/apis/sqladmin/v1beta4/rest) | Tables, instances, etc. |
 | VMs                         | Devices -> All Devices       | [Compute API](https://www.googleapis.com/discovery/v1/apis/compute/v1/rest) | Type, Name, RAM, OS, CPU, cores, etc. |
 
+Device42 also discovers the following GCP items:
+
+**Storage:**
+- Cloud Device
+- Cloud Disk
+
+**Networking:**
+- VPCs (VRF Groups)
+- VPC Firewall Rules
+- GCP Load Balancer
+
+**Databases:**
+- Cloud SQL
+- GCP BigQuery Table
+
+**Kubernetes:**
+- Kubernetes Cluster
+- Kubernetes Config Map
+- Kubernetes Container
+- Kubernetes Daemon Set
+- Kubernetes Deployment
+- Kubernetes Ingress
+- Kubernetes Ingress Rule
+- Kubernetes Namespace
+- Kubernetes Node
+- Kubernetes Persistent Volume
+- Kubernetes Pod
+- Kubernetes Quota
+- Kubernetes Replica Set
+- Kubernetes Replication Controller
+- Kubernetes Service
+- Kubernetes Service Port
+- Kubernetes Stateful Set
+- Kubernetes Volume
+
 ## GCP Permission Requirements
 
 The following permissions are required to perform a GCP discovery job. You can create a custom IAM role with these permissions or ensure they are included in existing roles granted to your account or service account.

docs/auto-discovery/database-discovery/index.mdx

@@ -7,7 +7,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 ## About Database Discovery
 
-Database (DB) discovery currently supports Windows and \*nix-based discovery jobs detecting Microsoft SQL (aka MSSQL), Oracle, Postgres SQL, and DB2 databases.
+Database (DB) discovery currently supports Windows and \*nix-based discovery jobs detecting Microsoft SQL (aka MSSQL), Oracle, PostgreSQL, and DB2 databases.
 
 :::note
 Database discovery requires an **Application Dependency Mapping** license. Go to **Tools > Settings > Licensing** to see if the license is enabled. Contact [[email protected]](mailto:[email protected]) for licensing assistance.
@@ -453,22 +453,22 @@ We've made the following changes to the UI:
 
 We previously gathered all Oracle users and collected them as "Device42 Databases." Then, we only retrieved Oracle users that had at least one associated database object, and from there, we implemented changes to ignore user schemas. As a result, some Oracle database connections may no longer show under specific user schemas. These 'orphaned' database connections now map to the main database instance, instead of mapping to a specific **Database/Schema** resource. While they’re not linked to individual schemas anymore, key details like the user login and schema names are still preserved in the database instance details.
 
-## Postgres SQL Database Discovery (on \*nix targets)
+## PostgreSQL Database Discovery (on \*nix targets)
 
-Device42 offers Postgres SQL database discovery for \*nix discovery targets, although it requires a separate set of credentials to authenticate to the database instance itself. Ensure these additional credentials have the appropriate permissions for viewing the databases you are interested in discovering.
+Device42 offers PostgreSQL database discovery for \*nix discovery targets, although it requires a separate set of credentials to authenticate to the database instance itself. Ensure these additional credentials have the appropriate permissions for viewing the databases you are interested in discovering.
 
-### Minimum Permissions Requirements for Postgres SQL Discovery
+### Minimum Permissions Requirements for PostgreSQL Discovery
 
 For discovery to return detailed information about your database instance, you will need access to the following tables:
 
-* `pg_database`
-* `pg_tablespace`
-* `pg_stat_activity`
-* `init_server_addr` (function)
+* `pg_database` (table)
+* `pg_tablespace` (table)
+* `pg_stat_activity` (table)
+* `⁠inet_server_addr()` (function)
 
-### Set Up Your Postgres SQL Discovery Job
+### Set Up Your PostgreSQL Discovery Job
 
-To begin discovering your Postgres SQL databases, create a new discovery job for \*nix targets, and be sure to enable database discovery by checking the **Collect database server information** checkbox.
+To begin discovering your PostgreSQL databases, create a new discovery job for \*nix targets, and be sure to enable database discovery by checking the **Collect database server information** checkbox.
 
 Fill out both sets of credentials:
 
@@ -503,7 +503,7 @@ sources={{
 }}
 />
 
-### View Postgres SQL Database Discovery Job Results
+### View PostgreSQL Database Discovery Job Results
 
 When the job finishes, the most direct way to view the results of your database discovery is via the discovered Postgres application components themselves. On the Device42 main menu, select **Applications > Application Components**. If you don’t see your Postgres DB instances at the top of the list, you can search for "Postgres" to narrow down the list, or filter the list **By Category > Database**.
 

docs/auto-discovery/linux-unix-server-auto-discovery.mdx

@@ -179,11 +179,11 @@ Specify the timeout range between 10 to 600 seconds in the **Timeout** field to
     }}
 />
 
-When discovery switches between *nix users, the triggered banner text messages may disrupt database discovery and Application Component creation, resulting in discovery errors or incomplete data collection. 
+If you experience unexplainable issues during discovery that you suspect are due to banner text interfering with parsing, enable the **Check for Banner** option for discovery to detect and remove banner messages. The **Check for Banner** option is also available via API.
 
-To ensure full data collection when switching users, enable the **Check for Banner** option for discovery to detect and remove banner messages.
+When discovery switches between *nix users, the triggered banner text messages may disrupt database discovery and Application Component creation, resulting in discovery errors or incomplete data collection. 
 
-The **Check for Banner** option is also available via API.
+Note that banner text interference can't be directly determined from Device42. You require a power user with system access to the target machine to detect interference by switching users. Device42 support may advise you to select the banner option if they suspect banner text interference.  
 
 <ThemedImage
     alt="Check for Banner option"

docs/auto-discovery/saas-discovery.mdx

@@ -45,7 +45,7 @@ The software data collected during SaaS discovery is available under the **Resou
 
 ### Discovered End Users
 
-You can find the end user discovery data under **Resources > Organization > End Users**. 
+You can find the end user discovery data under **Infrastructure > Organization > End Users**. 
 
 ### New and Existing End Users
 

docs/auto-discovery/warranty-autodiscovery.mdx

@@ -25,7 +25,7 @@ To configure automatic warranty discovery, you need to request API keys from the
 
 ### Detailed Warranty Sync Instructions
 
-Device42 supports warranty autodiscovery for the following vendors:**
+Device42 supports warranty autodiscovery for the following vendors:
 
 - Dell
 - IBM

docs/getstarted/discovery-hub.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Discovery Hub: scoping and onboarding"
+title: "Discovery Hub: Scoping and Onboarding"
 sidebar_position: 3.5
 ---
 
@@ -31,7 +31,7 @@ Log in to the Device42 UI and navigate to **Discovery > Discovery Hub**.
 
 To set up a Discovery Hub scan, name the scan and select the [Remote Collector](getstarted/installation/remote-collector-rc-installation.mdx) to use. You need to know the IPs, IP ranges, or CIDR blocks for your target environment.
 
-Enter the IP information in the box highlighted in the image below and click on the **+** button. You can enter as many targets as you like but the more targets included, the longer the scan will likely take. 
+Enter the IP information in the box highlighted in the image below and click on the **up arrow** button. You can enter as many targets as you like, but the more targets you include, the longer the scan will likely take. 
 
 <ThemedImage
   alt="Discovery Hub menu"
@@ -42,7 +42,7 @@ Enter the IP information in the box highlighted in the image below and click on
 />
 <br/><br/>
 
-After you have entered the information, click the bright green **Start** button. 
+After you have entered the IP address, named the scan, and selected at least one RC, click the green **Start** button. 
 
 The scan will start immediately. You'll see the green start notification, a percentage ticker showing your completion status, and information on the six categories of assets: **Windows**, **Nix**, **Network Devices**, **Hypervisors**, **Other/Unknown**, and **Unreachable**.
 
@@ -104,8 +104,8 @@ The scans you have created will be displayed in the left-hand column. Once start
 <ThemedImage
   alt="Scan results with settings button"
   sources={{
-    light: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-outcome-light.png'),
-    dark: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-outcome-dark.png'),
+    light: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-settings-button-light.png'),
+    dark: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-settings-button-dark.png'),
   }}
 />
 <br/><br/>
@@ -162,7 +162,9 @@ The **One-time discovery** and **Continuous discovery** options are recommended
     light: useBaseUrl('/assets/images/discovery-hub-onboarding/discovery-job-window-cidr-light.png'),
     dark: useBaseUrl('/assets/images/discovery-hub-onboarding/discovery-job-window-cidr-dark.png'),
   }}
+  style={{ width: '70%' }} 
 />
+
 <br/><br/>
 
 When the job is created successfully, you will see the screen below. You can close the window and go back to your scans or click the link to be taken to the job page to edit the job settings.
@@ -176,9 +178,7 @@ When the job is created successfully, you will see the screen below. You can clo
 />
 <br/><br/>
 
-From the **Settings** tab of completed Discovery Hub scans, you can see the linked jobs that were created based on those results. 
-
-Click on the **+ Add schedule button** to schedule the scan.
+From the **Settings** tab of completed Discovery Hub scans, you can see the linked jobs that were created based on those results. Click on the **+ Add schedule button** to schedule the scan.
 
 <ThemedImage
   alt="Network scan settings"

docs/getstarted/faqs/index.mdx

@@ -18,12 +18,7 @@ With a default configuration, visit `https://IP_or_fqdn_for_device42_vm` in your
 
 ## Which Browser Should I Use?
 
-Device42 recommends using the web browsers (or more recent versions) listed below.
-
-- Chrome — 88.0.4324.150
-- Edge — 88.0.705.63
-- Firefox — 72.0.1
-- Safari — 13.1.2 (13609.3.5.1.5)
+Device42 recommends using the latest version of Chrome, Firefox, Edge, or Safari.
 
 ## How Do I Get My Current Data Into Device42?
 
@@ -37,7 +32,7 @@ You can use any of the following tools to import your data to Device42:
 
 - [**Microsoft Excel / CSV (spreadsheet) import**](integration/imports/index.mdx): The **Tools > Imports/Exports (xls)** page outlines your options for importing MS Excel spreadsheets to Device42 and provides sample Excel sheets to help you format your existing spreadsheets so that uploading your existing data is as easy as possible.
 - [**Device42 generic import tool**](https://www.device42.com/blog/2018/06/19/new-features-added-to-the-generic-import-tool/): You can use the Device42 generic import tool to add and map fields for existing data from most spreadsheet formats. Learn more about formatting best practices in the Device42 walkthrough for manually [Importing Data From Existing Spreadsheets](getstarted/importing-data-from-existing-spreadsheets.mdx).
-- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as single source of truth for systems such as provisioning and monitoring.
+- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as a single source of truth for systems such as provisioning and monitoring.
 - **Device42 web UI**: You can use the Device42 web interface to import your data.
 - **Templates/bulk operations**: Certain object types are easier to add using templates or models. For example, it is easier to use [PDU models](infrastructure-management/power-units/defining-pdu-models.mdx) to create PDUs, [switch port templates](infrastructure-management/ipam/switch-templates.mdx) to create switches and ports, and [patch panel models](infrastructure-management/power-units/defining-pdu-models.mdx) to create patch panel ports and bulk backport connectivity for patch panels.
 
@@ -65,7 +60,7 @@ Current releases of Device42 support **all** discovery jobs, including WMI and P
 
 :::note
 RCs will only automatically update when an RC update coincides with an MA update.
-::
+:::
 
 ## How Do I Migrate Existing Power Appliance Jobs to a Remote Collector?
 
@@ -109,7 +104,7 @@ Data can be exported in Excel or CSV format by downloading current data from the
 
 ## How Do I Back Up My Data?
 
-Log in to the Device42 appliance manager at `https://your\_device42\_ip\_or\_FQDN:4242/` using the following default credentials:
+Log in to the Device42 appliance manager at `https://your_device42_ip_or_FQDN:4242/` using the following default credentials:
 
 - Username:`d42admin`
 - Password: `default`