diff --git a/docs/auto-discovery/database-discovery/index.mdx b/docs/auto-discovery/database-discovery/index.mdx index 7be64554..185315a9 100644 --- a/docs/auto-discovery/database-discovery/index.mdx +++ b/docs/auto-discovery/database-discovery/index.mdx @@ -7,35 +7,36 @@ import useBaseUrl from '@docusaurus/useBaseUrl' ## About Database Discovery -Database discovery was introduced in v16.02.00 _(ensure you are running v16.02+)_, and currently supports Windows and \*nix-based discovery jobs to discover Microsoft SQL (aka MSSQL), Oracle, Postgres SQL, and DB2 databases. +Database (DB) discovery was introduced in Device42 v16.02.00 and currently supports Windows and \*nix-based discovery jobs detecting Microsoft SQL (aka MSSQL), Oracle, Postgres SQL, 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 [support@device42.com](mailto:support@device42.com) for licensing assistance. +Database discovery requires an **Application Dependency Mapping** license. Go to **Tools > Settings > Licensing** to see if the license is enabled. Contact [support@device42.com](mailto:support@device42.com) for licensing assistance. ::: -By default, the target machine ports are defined by different database vendors as follows: -- MS SQL: 1433 -- DB2: 50000 +By default, the target machine ports are defined by the database vendors as follows: + +- Microsoft SQL (MSSQL): 1433 +- IBM DB2: 50000 - Postgres: 5432 - Oracle: 1521 -Dynamic discovery can discover different ports to use. As of v16.17.00, Device42 supports MSSQL and Oracle database discovery for customers that have database instances configured to listen on non-standard ports, especially on a shared database server hosting multiple instances. During database discovery, Device42 will identify and connect through the discovered active listening port. +Dynamic discovery detects which ports to use. As of v16.17.00, Device42 supports MSSQL and Oracle database discovery for customers with database instances configured to listen on non-standard ports, especially on shared database servers that host multiple instances. During database discovery, Device42 will identify and connect via the discovered active listening port. -If you want to specify DB discovery details yourself, including the DB server port, server IP address, and DB access credentials, use [Database Connections Discovery](#database-connections-discovery-jobs) jobs (see below) to discover databases. +If you want to specify database discovery details yourself, including the database server port, server IP address, and database access credentials, use [Database Connections Discovery](#database-connections-discovery-jobs) jobs (see below) to discover databases. ### Discovery Exclusions Set discovery exclusions in **Tools > Settings > Global Settings** in the **Discovery Exclusions** section. -If you enable the **Ignore DB Login Names** setting, DB login names will not be collected during database discovery. +If you enable the **Ignore DB Login Names** setting, database login names will not be collected during database discovery. You can also specify interfaces, IP addresses, and MAC addresses to be ignored during discovery. -## MS SQL Server DB Discovery (on Windows targets) +## MSSQL Server Database Discovery (on Windows Targets) -Microsoft SQL Server (MSSQL) discovery is supported on discovery targets running Microsoft Windows and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have appropriate permissions to view the databases you are interested in discovering. +Microsoft SQL Server (MSSQL) server discovery is supported on discovery targets running Microsoft Windows, although it requires a separate set of credentials to authenticate to the database instance itself. Ensure the discovery credentials have appropriate permissions to view the databases you are interested in discovering. -Device42 supports autodiscovery on Windows and \*nix platforms for the following MSSQL versions. +Device42 supports autodiscovery on Windows and \*nix platforms for the following MSSQL versions: - MSSQL 2005 - MSSQL 2008 @@ -47,69 +48,171 @@ Device42 supports autodiscovery on Windows and \*nix platforms for the following ### Minimum Permissions Requirements for MSSQL Discovery -To query the below tables, please ensure you have **View Server State** permissions. For discovery to return detailed info about your database instance, you will require read permissions to the following system views: +To query the tables below, please ensure you have **View Server State** permissions. For the discovery to return detailed information about your database instance, you need read permissions to the following system views: -
  • sys.dm_exec_connections
  • sys.dm_exec_sessions
  • sys.databases
  • sys.master_files
  • sys.tables
  • sys.dm_os_sys_info
  • sys.dm_os_sys_memory
  • sys.all_objects
+
  • `sys.dm_exec_connections`
  • `sys.dm_exec_sessions`
  • `sys.databases`
  • `sys.master_files`
  • `sys.tables`
  • `sys.dm_os_sys_info`
  • `sys.dm_os_sys_memory`
  • `sys.all_objects`
-The snippet shown below is necessary to get data from some of the preceding views even if the user has read permissions (_sys.master\_files_, for example). +The following snippet is necessary for retrieving data from some of the preceding views, such as `sys.master_files`, even when the user has read permissions enabled: -1 use \[master\] -2 GO -3 grant VIEW any DEFINITION TO \[discovery\_user\] -4 GO +```sql +USE [master]; +GO +GRANT VIEW ANY DEFINITION TO [discovery_user]; +GO +``` **Note**: The discovery user must belong to the administrator’s user group to discover databases successfully. -### Setting up your MSSQL discovery job +### Set Up Your MSSQL Discovery Job + +Create a new Windows discovery job under **Discovery > HyperVisors /\*nix /Windows** to discover MSSQL databases running on Windows. + +Enable database discovery by checking the **Collect database server information** checkbox. + + + +Be sure to fill out both sets of credentials: + +- **Database Username / Password(s):** Credentials for authenticating to the Microsoft SQL database itself. +- **Discovery Target(s) Credential(s):** Credentials for authenticating to the Windows server. -1) To begin discovering your MSSQL Databases \[running on Windows\], create a new Windows discovery job and be sure to enable database discovery by checking the **Collect database server information** checkbox. Select **Allow Unencrypted Connections** if you want to discover MSSQL 2005 or MSSQL 2008 databases. +Two sets of credentials must also be filled out for [regular Windows-based discovery targets](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx). -![](/assets/images/D42-21939_Unencrypted-conns-for-SQL-db-2.png) +You can enter an ordered list of preferred **Discovery Target(s) Credential(s)**. When the job runs, it will use the credentials in the order that you entered them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. -Be sure to fill out both sets of credentials – the first set (_Database Username / Password_) to authenticate to the Microsoft SQL database itself and the second (_Discovery Targets Credentials_) to authenticate to the Windows server itself (like you’re used to for [regular Windows-based discovery targets](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx)). + -You can enter an ordered list of preferred _Discovery Target(s) Credential(s)_ when you create a database discovery job. When the job runs, it will use the credentials in the order in which you enter them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. +Run the autodiscovery job to test it by clicking **Run Now** from the autodiscovery jobs list. -![](/assets/images/D42-21939_Unencrypted-conns-for-SQL-db-3-preferred-creds.png) +As MSSQL databases are detected, discovery will import a list of all the instances, databases, and connection details it finds. -* * * +You can see the status of the discovery job on the job setup page. Scroll down to the **Job Status** section and look for the bar graphs. ![Example job status](/assets/images/discovery-job-status-trimmed.png) -2) Kick off your discovery job to test it (select "Run now" on the Job Screen). As MSSQL databases are detected, discovery will import a list of all instances, databases, and connection details. You can see the status of the discovery job on the job's setup page, as well - Scroll down to the "Job Status" section and look for the bar graphs. +### View Your MSSQL Discovery Job Results + +Once the job finishes, there are multiple ways to view the results of your database discovery. -### Viewing MSSQL discovery job results +### Access Your Results Through the Discovered MSSQL Application Components -3) Once the job finishes, you can view the results of your database discovery. +The most direct method for viewing the discovered database details is via the discovered MSSQL application components themselves. -There are a couple of different ways to see the database details; the most direct is via the discovered MSSQL Application components themselves. Head to the Device42 main menu, Apps menu -> Application Components. If you don't see your SQL Server instances right at the top of the list, you can search for "SQL" to narrow the list down. +Navigate to the Device42 main menu and go to **Applications > Application Components**. If you don't see your SQL Server instances at the top of the list, you can search for "SQL" to narrow down the list. + +You can see the newly discovered SQL Server instances in the example below. Click on the **Name** of one of the application components to view more details. + + -You can see the newly discovered SQL Server instances in the example below -- Click any one of the Application Component Names for more details: +Scroll to the **Application Components** section at the bottom of the page and click the database instance name to view database details. -![MSSQL Application Components](/assets/images/Apps-Application-Components-menu-annotated.png) + -Scroll to the bottom, and click the database instance name to view database details: + -![](/assets/images/click-to-view-SQL-details.png) +For a rundown of the database details that discovery provides, jump to the [**Available SQL Database Instance Information**](#available-sql-database-instance-information) section. -For a rundown of the database details discovery provides, jump to the ["Available SQL database instance information"](#available-sql-database-instance-information) section. +### Another Way To View SQL Database Details -### Another way to view SQL Database details +Results are also available by browsing to the discovered Windows server instance's CI; either search for the device from the dashboard, via **Devices > All Devices**, or view your discovery job's results page and jump to the servers from there. You can also go to **Analytics > Discovery Scores** and search for the discovery job. -Results are also available by browsing to the discovered Windows server instance's CI; either search for the device from the dashboard, via "Devices -> All Devices", or view your discovery job's results/score page and jump to the servers from there: +Either search for the device from the dashboard, via **Devices > All Devices**, navigate to your discovery job results page and access the servers from there, or go to **Analytics > Discovery Scores** and search for your discovery job. ![](/assets/images/click-success-for-discovery-scores.png) -Click any of the "device names" (right-hand side) to jump to each discovered machine's details view. From the details view, you can simply click the "Services" tab to view a list of services, and can then click on the Microsoft SQL Server instance in that list. ![](/assets/images/discovery-score-to-view-1.png) +Click any of the **Object** names to view the details of the discovered machine. + + + +From the details view, open the **Services** tab to view a list of services, and click on the MSSQL Server instance in the **Service Detail** list. + + + +### Available SQL Database Instance Information + +The page displaying the database details includes lists that contain the following: + +- The **Resource Details** of the MSSQL database, including the **SQL Server Start Time** and memory stats. + + + +- The **Database/Schema** of the instance. You can click on each database for more details. -### Available SQL database instance information + -On the "View Database Instance" screen, you will see lists containing the following items: +- The **Database Instance Files**, including the **Creation Date** and **Path** for each resource. + + -- Databases on that instance _(each clickable for individual DB connection & size stats)_ -- Connections to that DB instance _(connection details available for each connection)_ -- Database size details, creation date, and path -- Extra details, including server start time, CPU count, Memory info, and more +- The **Endpoints and Network Details**. + + If your environment includes SQL cluster databases, discovery returns the following information about the clusters: @@ -119,17 +222,11 @@ If your environment includes SQL cluster databases, discovery returns the follow - Does Passive Node use Log Ship - Does Passive Node use DB Mirroring -A snippet from each section of the page can be seen below: +## Oracle Database Discovery (on Windows and \*nix targets) -![](/assets/images/database-list.png) ![](/assets/images/DB-Connection-Details.png) +Oracle database discovery (introduced in v16.04.00) is supported for Windows and \*nix discovery targets. Oracle discovery jobs require 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 want to discover. -![](/assets/images/database-size-details.png) ![](/assets/images/extra-DB-details.png) - -## Oracle DB Discovery (on Windows and \*nix targets) - -Oracle database discovery (introduced in v16.04.00) is supported for Windows and \*nix discovery targets and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have appropriate permissions to view the databases you are interested in discovering. - -As of v16.14.01, Device42 now supports autodiscovery on Windows and \*nix platforms for the following Oracle database versions. +As of v16.14.01, Device42 now supports autodiscovery on Windows and \*nix platforms for the following Oracle database versions: **Oracle 10g** @@ -158,15 +255,15 @@ As of v16.14.01, Device42 now supports autodiscovery on Windows and \*nix platfo - Windows 64 bit - CentOS 7 64 bit -As of v16.17.00, Device42 database autodiscovery for Windows and \*nix targets supports discovery for Oracle RAC clustered database environments. This will help users better assess their cluster databases and will enable users to better understand all IT assets that are tied to critical business applications. Discovery returns data about the RAC configuration, the RAC database, and the nodes (physical servers) running the RAC software. You can run the autodiscovery against one or more nodes in the Oracle RAC and return information about all connected nodes. We require the use of sudo for Oracle discoveries, without it lockout is a risk. +As of v16.17.00, Device42 database autodiscovery for Windows and \*nix targets supports discovery for Oracle RAC clustered database environments, which helps users better assess their cluster databases and understand all The IT assets tied to critical business applications. Discovery returns data about the RAC configuration, the RAC database, and the nodes (physical servers) running the RAC software. You can run the autodiscovery against one or more nodes in the Oracle RAC and return information about all connected nodes. Device42 requires the use of sudo for Oracle discoveries to mitigate the risk of lockout. ### Minimum Permissions Requirements for Oracle Discovery -For discovery to return detailed info about your database instance, you will require read/view permissions for the following system views/tables: +For discovery to return detailed info about your database instance, you will require read or view permissions for the following system views and tables:
  • V$SESSION
  • V$DATABASE
  • V$CONTAINERS
  • DBA_SEGMENTS
  • DBA_OBJECTS
  • SYS.ALL_USERS
  • DATABASE_COMPATIBLE_LEVEL
  • SYS.PRODUCT_COMPONENT_VERSION
-To get information about Pluggable Databases (PDBs) within a Container Database (CDB) in Oracle for non-DBA users, two key permission configurations are required: +To get information about pluggable databases (PDBs) within an Oracle container database (CDB), two key permission configurations are required for non-DBA users: - SELECT permission on the V$CONTAINERS view. - Set `container_data=all container=current` for context configuration. For example: @@ -178,45 +275,107 @@ To get information about Pluggable Databases (PDBs) within a Container Database CONTAINER = CURRENT; ``` -### Setting up your Oracle discovery job +### Set Up Your Oracle Discovery Job + +To begin discovering your Oracle databases, navigate to **Discovery > HyperVisors /\*nix /Windows**. Create a new discovery job for Windows or \*nix (or both) targets, and be sure to check the **Collect database server information** checkbox. + + + +Be sure to fill out both sets of credentials: -1) To begin discovering your Oracle databases, create a new discovery job for Windows or \*nix (or both) targets, and be sure to check the **Collect database server information** checkbox. +- **Database Username / Password(s)** to authenticate to the Oracle database. +- **Discovery Target(s) Credential(s)** to authenticate to the Windows or *nix server. -Be sure to fill out both sets of credentials – the first set (_Database Username / Password_) to authenticate to the Oracle database itself and the second (_Discovery Targets Credentials_) to authenticate to the Windows or \*nix server itself. +You can enter an ordered list of preferred **Discovery Target(s) Credential(s)** when you create a database discovery job. When the job runs, it will use the credentials in the order that you entered them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. -You can enter an ordered list of preferred _Discovery Target(s) Credential(s)_ when you create a database discovery job. When the job runs, it will use the credentials in the order in which you enter them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. + + +Run your new discovery job to test it. Click **Run Now** for the job on the list page under **Discovery > HyperVisors /\*nix /Windows**. As Oracle databases are detected, discovery will import a list of all the instances, databases, and connection details it finds. -![](/assets/images/D42-21939_Oracle-db-discovery.png) + -2) Kick off your new discovery job to test it (select **Run Now** on the Jobs screen). As Oracle databases are detected, discovery will import a list of all instances, databases, and connection details. +### View Oracle Database Discovery Job Results -![](/assets/images/Oracle-Discovery-1a-3.png) +When the job finishes, the most direct way to view the results of your database discovery is via the discovered Oracle application components. -### Viewing Oracle DB discovery job results +On the Device42 main menu, select **Applications > Application Components**. If you don't see your Oracle database instances at the top of the list, you can search for "Oracle" to narrow down the list. -3) Once the job finishes, you can view the results of your database discovery. There are a couple of different ways to see the database details; the most direct is via the discovered Oracle Application components themselves. On the Device42 main menu, select **Apps -> Application Components**. If you don't see your Oracle DB instances right at the top of the list, you can search for _Oracle_ to narrow down the list. + -![](/assets/images/Oracle-Discovery-2a-4.png) +Click on a database name on the **Application Components** list page to view the details of that specific application component. On the **View Application Component** page, click the **ellipsis icon** to view the database **Dependency Chart**, **Impact Chart**, **Impact List**, **Passwords**, and **Details**. -Use the View Database Instances screen to view a list of discovered databases. + -![](/assets/images/Oracle-Discovery-7-DB-Instance.png) +Example Oracle database dependency chart: -Scroll down through the screen to see a list of database connections and sizes. + -![](/assets/images/Oracle-Discovery-7a-DB-Connections.png) -![](/assets/images/Oracle-Discovery-7b-DB-Sizes.png) +You can scroll down the **View Application Component** page to see a list of the Oracle database **Service Instances**. -You can also click on the database name on the View Database Instances screen to see its connection and size data. + -![](/assets/images/Oracle-Discovery-7c-DB-ByName.png) +Scroll further down to see **Software** and **Database Instances** associated with the Oracle database. -On the Application Components screen, click **Show** to view the database Dependency Chart or an Impact Chart or List. + -![](/assets/images/Oracle-Discovery-5-Dependency-Chart.png) +You can click on a database instance to view more details, including **Containers** and **Database/Schema** information. -![](/assets/images/Oracle-Discovery-3a-4.png) + ### Oracle CDB/PDB Matching Process and Regular Processing Procedures @@ -230,97 +389,146 @@ We don't aim to match orphaned PDBs to the CDB if a fresh CDB is incoming. If a candidate database instance is detected to be a child of a CDB we skip the matching process -## Postgres SQL DB Discovery (on \*nix targets) +## Postgres SQL Database Discovery (on \*nix targets) -Postgres SQL database discovery (introduced in v17.11.00) is for \*nix discovery targets and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have appropriate permissions to view the databases you are interested in discovering. +From v17.11.00 onward, 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. ### Minimum Permissions Requirements for Postgres SQL Discovery -For discovery to return detailed info about your database instance, you will need access to the tables: +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) + +### Set Up Your Postgres SQL Discovery Job -* pg_database -* pg_tablespace -* pg_stat_activity -* init_server_addr (function) +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. -### Setting up your Postgres SQL discovery job +Fill out both sets of credentials: -1) 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. +- **Database Username / Password(s):** These credentials are used to authenticate to the Postgres database. +- **Discovery Target(s) Credential(s):** These credentials are used to authenticate to the \*nix server. + + -Be sure to fill out both sets of credentials – the first set (_Database Username / Password_) to authenticate to the Postgres database itself and the second (_Discovery Targets Credentials_) to authenticate to the \*nix server itself. +You can enter an ordered list of preferred **Discovery Target(s) Credential(s)** when you create a database discovery job. When the job runs, it will use the credentials in the order that you entered them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. -You can enter an ordered list of preferred _Discovery Target(s) Credential(s)_ when you create a database discovery job. When the job runs, it will use the credentials in the order in which you enter them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. + -![](/assets/images/D42-23580_Postgres-ad-job-edit-page.png) +Run your new discovery job to test it. Click **Run Now** for the job on the list page under **Discovery > HyperVisors /\*nix /Windows**. As Postgres databases are detected, discovery will import a list of all the instances, databases, and connection details it finds. -2) Kick off your new discovery job to test it (select **Run Now** on the discovery jobs screen). As Postgres databases are detected, discovery will import a list of all instances, databases, and connection details. + -### Viewing Postgres SQL DB discovery job results +### View Postgres SQL Database Discovery Job Results -3) Once the job finishes, you can view the results of your database discovery. There are a couple of different ways to see the database details; the most direct 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 right at the top of the list, you can search for _Postgres_ to narrow down the list, or filter the list **By Category > Database**. +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**. -![](/assets/images/postgresSQL.jpg) + -You can also select **Resources > Databases > On-Prem Databases** to display a list of databases. +You can also select **Resources > Databases > On-Prem Databases** to display a list of databases. -![](/assets/images/AD2-700x407.png) + ## DB2 Discovery (on \*nix targets) -DB2 database discovery (introduced in v18.02.00) is for \*nix discovery targets and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have appropriate permissions to view the databases you are interested in discovering. +DB2 database discovery (introduced in v18.02.00) is for \*nix discovery targets and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have the appropriate permissions for viewing the databases you are interested in discovering. ### Permissions for DB2 Discovery For discovery to return detailed info about your database instance, you will require the following permissions: **1. Privileges for ENV_SYS_INFO:** - - SELECT or CONTROL privilege on the ENV_SYS_INFO administrative view - - EXECUTE privilege on the ENV_GET_SYS_INFO table function + + - **SELECT** or **CONTROL** privilege on the `ENV_SYS_INFO` administrative view. + - **EXECUTE** privilege on the `ENV_GET_SYS_INFO` table function. **2. Privileges for SNAPAPPL_INFO:** - - SELECT or CONTROL privilege on the SNAPAPPL_INFO administrative view - - EXECUTE privilege on the SNAP_GET_APPL_INFO_V95 table function OR DATAACCESS authority + + - **SELECT** or **CONTROL** privilege on the `SNAPAPPL_INFO` administrative view + - **EXECUTE** privilege on the `SNAP_GET_APPL_INFO_V95` table function or **DATAACCESS** authority. **3. Privileges for ENV_INST_INFO:** - - SELECT or CONTROL privilege on the ENV_INST_INFO administrative view - - DATAACCESS authority OR DBADM authority OR SQLADM authority OR ACCESSCTRL authority OR SECADM authority + + - **SELECT** or **CONTROL** privilege on the `ENV_INST_INFO` administrative view + - One of the following authorities: **DATAACCESS**, **DBADM**, **SQLADM**, **ACCESSCTRL**, or **SECADM**. **4. Privileges for DBCFG:** - - SELECT or CONTROL privilege on the DBCFG administrative view - - DATAACCESS authority OR DBADM authority OR SQLADM authority + + - **SELECT** or **CONTROL** privilege on the `DBCFG` administrative view + - One of the following authorities: **DATAACCESS**, **DBADM**, or **SQLADM**. **5. Privileges for CONTAINER_UTILIZATION:** - - SELECT or CONTROL privilege on the CONTAINER_UTILIZATION administrative view - - DATAACCESS authority OR DBADM authority OR SQLADM authority OR ACCESSCTRL authority OR SECADM authority + + - **SELECT** or **CONTROL** privilege on the `CONTAINER_UTILIZATION` administrative view. + - One of the following authorities: **DATAACCESS**, **DBADM**, **SQLADM**, **ACCESSCTRL**, or **SECADM**. **6. Privileges for Monitoring:** - - EXECUTE privilege on the MON_GET_CONNECTION - - DATAACCESS authority OR DBADM authority OR SQLADM authority + + - **EXECUTE** privilege on the `MON_GET_CONNECTION`. + - One of the following authorities: `DATAACCESS`, `DBADM`, or `SQLADM`. **7. Privileges for Routines:** - - EXECUTE privilege on the GET_DBSIZE_INFO, WLM_SET_CONN_ENV, MON_GET_CONTAINER, and MON_GET_TABLESPACE routines - - DATAACCESS authority OR DBADM authority OR SQLADM authority + + - **EXECUTE** privilege on the `GET_DBSIZE_INFO`, `WLM_SET_CONN_ENV`, `MON_GET_CONTAINER`, and `MON_GET_TABLESPACE` routines. + - One of the following authorities: **DATAACCESS**, **DBADM**, or **SQLADM**. **Additional SELECT Privileges:** - - SELECT privilege on the SYSIBM.SYSTABLESPACES - - SELECT privilege on the SYSIBM.SYSDUMMY1 - - SELECT privilege on the SYSIBM.SYSVERSIONS + + - SELECT privilege on the `SYSIBM.SYSTABLESPACES` + - SELECT privilege on the `SYSIBM.SYSDUMMY1` + - SELECT privilege on the `SYSIBM.SYSVERSIONS` **Required Authorities:** + - One of the following authorities is required for overall access: - - SYSMON - - SYSMAINT - - SYSCTRL - - SYSADM + - **SYSMON** + - **SYSMAINT** + - **SYSCTRL** + - **SYSADM** -### Setting up your DB2 discovery job +### Set Up Your DB2 Discovery Job -To begin discovering your DB2 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 DB2 databases, create a new discovery job for \*nix targets, and be sure to enable database discovery by checking the **Collect database server information** checkbox. -Be sure to fill out both sets of credentials – the first set (_Database Username / Password_) to authenticate to the DB2 database itself and the second (_Discovery Targets Credentials_) to authenticate to the \*nix server itself. +Be sure to fill out both sets of credentials. -You can enter an ordered list of preferred _Discovery Target(s) Credential(s)_ when you create a database discovery job. When the job runs, it will use the credentials in the order in which you enter them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. +- **Database Username / Password(s):** These credentials are used to authenticate to the DB2 database. +- **Discovery Target(s) Credential(s):** These credentials are used to authenticate to the \*nix server itself. + +You can enter an ordered list of preferred **Discovery Target(s) Credential(s)** when you create a database discovery job. When the job runs, it will use the credentials in the order that you entered them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list. -### Viewing DB2 discovery job results +### View DB2 Discovery Job Results + +When the job finishes, you can view the results of your database discovery. Discovered DB2 databases are added to the **On-Prem Databases** list page. -Once the job finishes, you can view the results of your database discovery. Discovered DB2 databases are added to the On-Prem Databases list page. On the Device42 main menu, select **Resources -> Databases > On-Prem Databases** to display the page. If you don’t see your DB2 instances, you can search for _DB2_ to narrow down the list. +On the Device42 main menu, select **Resources > Databases > On-Prem Databases** to display the page. If you don’t see your DB2 instances, you can search for "DB2" to narrow down the list. -Click on your DB2 instance name under the _Resource Name_ column to see more information about that database. +Click on your DB2 instance name under the **Resource Name** column to view more information about the database. Database** from the main menu to display the Database discovery list page. +- Select **Discovery > Database** from the main menu to display the **Database Discoveries** list page. + + + +- Click on a database discovery name to view that job. Click **+ Add** on the top right of the page to add a new database discovery job. -![](/assets/images/discovery-database-menu.png) + -- Click on a Database discovery _Name_ to view that job. Click **+Add** at the top right of the page to add a new Database discovery job. +- Click **Edit** on the bottom right of the page to edit an existing job. Click **+ Add More** to add additional database connection information for the job. -![](/assets/images/database-discovery-list.png) + -- Click **Edit** at the bottom right of the page to edit an existing job. Click **+Add More** to add additional Database Connection information for the job. +- Enter or select the **Database Connections** information: -![](/assets/images/D42-25010_db-AD-job-1.png) + - **Name:** Connection name + - **Application Component:** Application component to link to + - **Platform:** Database type: Oracle, MS SQL, Postgres, or DB2 + - **Server:**  IP address of the DB server + - **Port:** DB server port + - **Credential:** DB server access credentials + - **Extra:** Enter a name specific to the database type: -- Enter or select the Database Connections information: - - **Name** – Connection name - - **Application Component** – Application Component to link to - - **Platform** – Database type: Oracle, MS SQL, Postgres or DB2 - - **Server** –  IP address of the DB server - - **Port** – DB server port - - **Credential** – DB server access credentials - - **Extra** – Specific to the database type:  - - _Instance_ for Oracle (required) - - _Database_ for Postgres and DB2 (required) + - Enter an **Instance:** name for Oracle (required) + - Enter a **Database:** name for Postgres and DB2 (required) - Not required for MS SQL -- Use the **trash can icon** to remove a Connections line. -- Scroll down the page to add or edit the **Discovery Schedule** for the job. -- Click **Save** to save the job. +- Use the **trash can icon** to remove a **Database Connections** line. +- Scroll down the page to add or edit the **Discovery Schedule** for the job. +- Click **Save** to save the job. ### Database Discovery Job Scores -You can view Discovery Scores for Database jobs that have run. +You can view **Discovery Scores** for the database jobs that have been run. -- Navigate to **Analytics > Discovery Status > Discovery Scores** to display the Discovery Scores page. +- Navigate to **Analytics > Discovery Status > Discovery Scores** to display the **Discovery Scores** page.

-- Click on the job you want to see under the **Discovery Target** column. You can use the search bar and/or the dropdown menu options next to it to find a specific database or narrow down your results. +- Click on the job you want to view in the **Discovery Target** column. You can use the search bar or the **Select an action** dropdown menu options to find a specific database or narrow down your results.

-- Click on **Detailed Discovery Scores** to see additional information. +- Click **Detailed Discovery Scores** to see additional information. Databases > On-Prem Databases** to display the list page. +Discovered databases are added to the **On-Prem Databases** list page. -![](/assets/images/on-prem-databases-menu.png) +- Select **Resources > Databases > On-Prem Databases** to display the list page. + + -- Click on the name of the database you want to see in the _Resource Name_ column. +- Click on the name of the database you want to see in the **Resource Name** column. -![](/assets/images/on-prem-databases-resource-name.png) + diff --git a/docs/auto-discovery/load-balancer-f5-autodiscovery.md b/docs/auto-discovery/load-balancer-f5-autodiscovery.md index 9a5af870..ae761c8d 100644 --- a/docs/auto-discovery/load-balancer-f5-autodiscovery.md +++ b/docs/auto-discovery/load-balancer-f5-autodiscovery.md @@ -21,7 +21,7 @@ For F5 discovery, ensure you have a **local username** with access to the F5 API If you're discovering an F5, do the following. You'll want to scan your F5 pool members via either SSH or the API, depending on the device's OS. -1. Start by scanning an F5 device via SNMP. Do this by adding a job under _Discovery → SNMP_ (Make sure you configure SNMP on your F5!), and input the correct (matching) community string. See the [Load Balancers](auto-discovery/load-balancers.md) page for more information about SNMP discovery. +1. Start by scanning an F5 device via SNMP. Do this by adding a job under _Discovery → SNMP_ (Make sure you configure SNMP on your F5!), and input the correct (matching) community string. See the [Load Balancers](auto-discovery/load-balancers.mdx) page for more information about SNMP discovery. 2. After you've discovered via SNMP, go ahead and scan the F5 with the native F5 interface that can be found in _Discovery -> _UCS/ACI/Load Balancers_._ _(Note: This requires an account w/ F5 API permissions!)_. - For other load balancer types, select the _Platform_ for that type from the drop-down menu. diff --git a/docs/auto-discovery/load-balancers.md b/docs/auto-discovery/load-balancers.md deleted file mode 100644 index 16f24e24..00000000 --- a/docs/auto-discovery/load-balancers.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: "Load Balancers" -sidebar_position: 18 ---- - -## Introduction - -Device42 SNMP autodiscovery provides a new option for F5 load balancer discovery that returns discovered load balancers as both devices and Managed Resources. Discovering F5 load balancers as managed resources provides additional details about the load balancers and related resources that include resource maps that visually show the relationships between load balancers and their related resources. It also simplifies the chart view for Affinity Groups by visually presenting the servers underneath a load balancer. - -The recommended best practice for Load balancer discovery is to first identify the devices using SNMP. This will identify the devices and associated resources. Next perform a Windows/*nix discovery of the back end resources to get more detailed inforamtion. Once you have the devices discovered you can then perform the API based "Load Balancer" discovery to link the devices correctly. - -## Managed Resources Views - -Discovered F5 load balancers are included in the Managed Resources list. Select _Resources > Managed Resources_ from the Device42 menu to display the list. See the [Managed Resources](https://docs.device42.com/auto-discovery/resources/) page for more information. - -Click the _Vendor Resource Type_ filter drop-down and select _F5_ to display load balancer resources. - -![](/assets/images/Load-Balancers_resources-listdrop-down.png) - -  - -Click on a load balancer _Resource Name_ to see details about that load balancer. You can use the links in the panel on the right to see details about related resources. - -![](/assets/images/Load-Balancers_single-resource-props.png) - -  - -Click _Resource Map_ at the top left of the page to see the topography map for the resource. You can select which _Resource Types_ you want to include in the map. - -![](/assets/images/Load-Balancers_cluster-map.png) - -The image below shows another example resource map for clustered load balancers. - -![](/assets/images/Load-Balancers_single-map.png) - -You will notice that the Chart views for Affinity Groups are now much simpler and easier to understand. Select _Applications > Affinity Groups_ to display the affinity group list. - -![](/assets/images/Load-Balancers_AG-list.png) - -Click the _Chart_ link to view the chart for an affinity group with a load balancer. - -![](/assets/images/Load-Balancers_AG-chart.png) diff --git a/docs/auto-discovery/load-balancers.mdx b/docs/auto-discovery/load-balancers.mdx new file mode 100644 index 00000000..dc64ee45 --- /dev/null +++ b/docs/auto-discovery/load-balancers.mdx @@ -0,0 +1,57 @@ +--- +title: "Load Balancers" +sidebar_position: 18 +--- + +import ThemedImage from '@theme/ThemedImage' +import useBaseUrl from '@docusaurus/useBaseUrl' + +## Introduction + +The Device42 Simple Network Management Protocol (SNMP) autodiscovery provides a new option for F5 load balancer discovery that returns discovered load balancers as both devices and managed resources. Discovering F5 load balancers as managed resources provides you with additional details about the load balancers and their related resources, including resource maps that visually represent the relationships between load balancers and resources, and simplifies the Affinity Groups chart view by placing the servers beneath a load balancer. + +The recommended best practice for Load balancer discovery is to first identify the devices using SNMP. This will identify the devices and associated resources. Next perform a Windows/*nix discovery of the back end resources to get more detailed inforamtion. Once you have the devices discovered you can then perform the API based "Load Balancer" discovery to link the devices correctly. + +## Managed Resources Views + +Discovered F5 load balancers are included in the **Resources** list. Navigate to **Resources > All Resources** from the Device42 menu to display the list page. You can consult the Device42 [Managed Resources](resources/index.mdx) documentation for more information. + +Click the **Vendor Resource Type** dropdown and check "F5" to filter the list for load balancer resources. + + + +Click on a load balancer in the **Resource Name** column to view more details about that load balancer. You can use the links in the right-hand panel to see details about related resources. + + + +Click **Resource Map** on the top left of the load balancer details page to view the topography map for the resource. In the **Tools & Breakdown** section of the left-hand panel, you can view, add, highlight, and search items to include in the map according to their resource type. + +The image below shows an example resource map for clustered load balancers. + + + +The chart views for affinity groups are now much simpler and easier to understand. Navigate to **Applications > Affinity Groups** from the Device42 main menu to display the **Affinity Groups** list page. + +![](/assets/images/Load-Balancers_AG-list.png) + +Click on **Chart** to view the chart for an affinity group with a load balancer. + +![](/assets/images/Load-Balancers_AG-chart.png) diff --git a/static/assets/images/database-discovery/add-db-connections-dark.png b/static/assets/images/database-discovery/add-db-connections-dark.png new file mode 100644 index 00000000..a954d392 Binary files /dev/null and b/static/assets/images/database-discovery/add-db-connections-dark.png differ diff --git a/static/assets/images/database-discovery/add-db-connections-light.png b/static/assets/images/database-discovery/add-db-connections-light.png new file mode 100644 index 00000000..6d62fa58 Binary files /dev/null and b/static/assets/images/database-discovery/add-db-connections-light.png differ diff --git a/static/assets/images/database-discovery/application-components-search-dark.png b/static/assets/images/database-discovery/application-components-search-dark.png new file mode 100644 index 00000000..0dadfa53 Binary files /dev/null and b/static/assets/images/database-discovery/application-components-search-dark.png differ diff --git a/static/assets/images/database-discovery/application-components-search-light.png b/static/assets/images/database-discovery/application-components-search-light.png new file mode 100644 index 00000000..4deb1175 Binary files /dev/null and b/static/assets/images/database-discovery/application-components-search-light.png differ diff --git a/static/assets/images/database-discovery/database-schema-dark.png b/static/assets/images/database-discovery/database-schema-dark.png new file mode 100644 index 00000000..9d5b04bc Binary files /dev/null and b/static/assets/images/database-discovery/database-schema-dark.png differ diff --git a/static/assets/images/database-discovery/database-schema-light.png b/static/assets/images/database-discovery/database-schema-light.png new file mode 100644 index 00000000..b4dd8228 Binary files /dev/null and b/static/assets/images/database-discovery/database-schema-light.png differ diff --git a/static/assets/images/database-discovery/db-discoveries-list-pg-dark.png b/static/assets/images/database-discovery/db-discoveries-list-pg-dark.png new file mode 100644 index 00000000..79ed1fa1 Binary files /dev/null and b/static/assets/images/database-discovery/db-discoveries-list-pg-dark.png differ diff --git a/static/assets/images/database-discovery/db-discoveries-list-pg-light.png b/static/assets/images/database-discovery/db-discoveries-list-pg-light.png new file mode 100644 index 00000000..de7af07a Binary files /dev/null and b/static/assets/images/database-discovery/db-discoveries-list-pg-light.png differ diff --git a/static/assets/images/database-discovery/db-discovery-menu-dark.png b/static/assets/images/database-discovery/db-discovery-menu-dark.png new file mode 100644 index 00000000..6e94f709 Binary files /dev/null and b/static/assets/images/database-discovery/db-discovery-menu-dark.png differ diff --git a/static/assets/images/database-discovery/db-discovery-menu-light.png b/static/assets/images/database-discovery/db-discovery-menu-light.png new file mode 100644 index 00000000..e1ab3e1b Binary files /dev/null and b/static/assets/images/database-discovery/db-discovery-menu-light.png differ diff --git a/static/assets/images/database-discovery/db-instance-files-dark.png b/static/assets/images/database-discovery/db-instance-files-dark.png new file mode 100644 index 00000000..c75738f6 Binary files /dev/null and b/static/assets/images/database-discovery/db-instance-files-dark.png differ diff --git a/static/assets/images/database-discovery/db-instance-files-light.png b/static/assets/images/database-discovery/db-instance-files-light.png new file mode 100644 index 00000000..e5c0c04c Binary files /dev/null and b/static/assets/images/database-discovery/db-instance-files-light.png differ diff --git a/static/assets/images/database-discovery/db-on-prem-menu-dark.png b/static/assets/images/database-discovery/db-on-prem-menu-dark.png new file mode 100644 index 00000000..3bf64c70 Binary files /dev/null and b/static/assets/images/database-discovery/db-on-prem-menu-dark.png differ diff --git a/static/assets/images/database-discovery/db-on-prem-menu-light.png b/static/assets/images/database-discovery/db-on-prem-menu-light.png new file mode 100644 index 00000000..533b6634 Binary files /dev/null and b/static/assets/images/database-discovery/db-on-prem-menu-light.png differ diff --git a/static/assets/images/database-discovery/discovery-scores-dark.png b/static/assets/images/database-discovery/discovery-scores-dark.png new file mode 100644 index 00000000..7b48fb44 Binary files /dev/null and b/static/assets/images/database-discovery/discovery-scores-dark.png differ diff --git a/static/assets/images/database-discovery/discovery-scores-light.png b/static/assets/images/database-discovery/discovery-scores-light.png new file mode 100644 index 00000000..2ebb4829 Binary files /dev/null and b/static/assets/images/database-discovery/discovery-scores-light.png differ diff --git a/static/assets/images/database-discovery/discovery-targets-credentials-dark.png b/static/assets/images/database-discovery/discovery-targets-credentials-dark.png new file mode 100644 index 00000000..718c20c5 Binary files /dev/null and b/static/assets/images/database-discovery/discovery-targets-credentials-dark.png differ diff --git a/static/assets/images/database-discovery/discovery-targets-credentials-light.png b/static/assets/images/database-discovery/discovery-targets-credentials-light.png new file mode 100644 index 00000000..5d72bf7a Binary files /dev/null and b/static/assets/images/database-discovery/discovery-targets-credentials-light.png differ diff --git a/static/assets/images/database-discovery/endpoints-network-dark.png b/static/assets/images/database-discovery/endpoints-network-dark.png new file mode 100644 index 00000000..2b6d2132 Binary files /dev/null and b/static/assets/images/database-discovery/endpoints-network-dark.png differ diff --git a/static/assets/images/database-discovery/endpoints-network-light.png b/static/assets/images/database-discovery/endpoints-network-light.png new file mode 100644 index 00000000..9c284a15 Binary files /dev/null and b/static/assets/images/database-discovery/endpoints-network-light.png differ diff --git a/static/assets/images/database-discovery/mssql-db-instances-dark.png b/static/assets/images/database-discovery/mssql-db-instances-dark.png new file mode 100644 index 00000000..16afc986 Binary files /dev/null and b/static/assets/images/database-discovery/mssql-db-instances-dark.png differ diff --git a/static/assets/images/database-discovery/mssql-db-instances-light.png b/static/assets/images/database-discovery/mssql-db-instances-light.png new file mode 100644 index 00000000..a0702fc9 Binary files /dev/null and b/static/assets/images/database-discovery/mssql-db-instances-light.png differ diff --git a/static/assets/images/database-discovery/mssql-example-dark.png b/static/assets/images/database-discovery/mssql-example-dark.png new file mode 100644 index 00000000..979efa0c Binary files /dev/null and b/static/assets/images/database-discovery/mssql-example-dark.png differ diff --git a/static/assets/images/database-discovery/mssql-example-light.png b/static/assets/images/database-discovery/mssql-example-light.png new file mode 100644 index 00000000..216c3c85 Binary files /dev/null and b/static/assets/images/database-discovery/mssql-example-light.png differ diff --git a/static/assets/images/database-discovery/new-sql-discovery-job-dark.png b/static/assets/images/database-discovery/new-sql-discovery-job-dark.png new file mode 100644 index 00000000..27f55e53 Binary files /dev/null and b/static/assets/images/database-discovery/new-sql-discovery-job-dark.png differ diff --git a/static/assets/images/database-discovery/new-sql-discovery-job-light.png b/static/assets/images/database-discovery/new-sql-discovery-job-light.png new file mode 100644 index 00000000..690d475f Binary files /dev/null and b/static/assets/images/database-discovery/new-sql-discovery-job-light.png differ diff --git a/static/assets/images/database-discovery/on-prem-db-list-pg-dark.png b/static/assets/images/database-discovery/on-prem-db-list-pg-dark.png new file mode 100644 index 00000000..f069437f Binary files /dev/null and b/static/assets/images/database-discovery/on-prem-db-list-pg-dark.png differ diff --git a/static/assets/images/database-discovery/on-prem-db-list-pg-light.png b/static/assets/images/database-discovery/on-prem-db-list-pg-light.png new file mode 100644 index 00000000..331efb18 Binary files /dev/null and b/static/assets/images/database-discovery/on-prem-db-list-pg-light.png differ diff --git a/static/assets/images/database-discovery/oracle-app-components-dark.png b/static/assets/images/database-discovery/oracle-app-components-dark.png new file mode 100644 index 00000000..3237dadf Binary files /dev/null and b/static/assets/images/database-discovery/oracle-app-components-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-app-components-light.png b/static/assets/images/database-discovery/oracle-app-components-light.png new file mode 100644 index 00000000..9f1a0672 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-app-components-light.png differ diff --git a/static/assets/images/database-discovery/oracle-chart-options-dark.png b/static/assets/images/database-discovery/oracle-chart-options-dark.png new file mode 100644 index 00000000..fc013f04 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-chart-options-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-chart-options-light.png b/static/assets/images/database-discovery/oracle-chart-options-light.png new file mode 100644 index 00000000..8d32db73 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-chart-options-light.png differ diff --git a/static/assets/images/database-discovery/oracle-db-instance-dark.png b/static/assets/images/database-discovery/oracle-db-instance-dark.png new file mode 100644 index 00000000..941d3158 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-db-instance-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-db-instance-light.png b/static/assets/images/database-discovery/oracle-db-instance-light.png new file mode 100644 index 00000000..eae105c8 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-db-instance-light.png differ diff --git a/static/assets/images/database-discovery/oracle-dependency-chart-dark.png b/static/assets/images/database-discovery/oracle-dependency-chart-dark.png new file mode 100644 index 00000000..288cf04f Binary files /dev/null and b/static/assets/images/database-discovery/oracle-dependency-chart-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-dependency-chart-light.png b/static/assets/images/database-discovery/oracle-dependency-chart-light.png new file mode 100644 index 00000000..9f0ca2ba Binary files /dev/null and b/static/assets/images/database-discovery/oracle-dependency-chart-light.png differ diff --git a/static/assets/images/database-discovery/oracle-job-basics-dark.png b/static/assets/images/database-discovery/oracle-job-basics-dark.png new file mode 100644 index 00000000..35e90d38 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-job-basics-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-job-basics-light.png b/static/assets/images/database-discovery/oracle-job-basics-light.png new file mode 100644 index 00000000..ffb126aa Binary files /dev/null and b/static/assets/images/database-discovery/oracle-job-basics-light.png differ diff --git a/static/assets/images/database-discovery/oracle-run-now-dark.png b/static/assets/images/database-discovery/oracle-run-now-dark.png new file mode 100644 index 00000000..5608a452 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-run-now-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-run-now-light.png b/static/assets/images/database-discovery/oracle-run-now-light.png new file mode 100644 index 00000000..318dfad3 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-run-now-light.png differ diff --git a/static/assets/images/database-discovery/oracle-service-instances-dark.png b/static/assets/images/database-discovery/oracle-service-instances-dark.png new file mode 100644 index 00000000..66afc748 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-service-instances-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-service-instances-light.png b/static/assets/images/database-discovery/oracle-service-instances-light.png new file mode 100644 index 00000000..67710845 Binary files /dev/null and b/static/assets/images/database-discovery/oracle-service-instances-light.png differ diff --git a/static/assets/images/database-discovery/oracle-software-and-instances-dark.png b/static/assets/images/database-discovery/oracle-software-and-instances-dark.png new file mode 100644 index 00000000..2965a03c Binary files /dev/null and b/static/assets/images/database-discovery/oracle-software-and-instances-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-software-and-instances-light.png b/static/assets/images/database-discovery/oracle-software-and-instances-light.png new file mode 100644 index 00000000..1b4aabaf Binary files /dev/null and b/static/assets/images/database-discovery/oracle-software-and-instances-light.png differ diff --git a/static/assets/images/database-discovery/oracle-target-credentials-dark.png b/static/assets/images/database-discovery/oracle-target-credentials-dark.png new file mode 100644 index 00000000..10b93fdc Binary files /dev/null and b/static/assets/images/database-discovery/oracle-target-credentials-dark.png differ diff --git a/static/assets/images/database-discovery/oracle-target-credentials-light.png b/static/assets/images/database-discovery/oracle-target-credentials-light.png new file mode 100644 index 00000000..77bb706c Binary files /dev/null and b/static/assets/images/database-discovery/oracle-target-credentials-light.png differ diff --git a/static/assets/images/database-discovery/postgres-app-components-dark.png b/static/assets/images/database-discovery/postgres-app-components-dark.png new file mode 100644 index 00000000..156af4d5 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-app-components-dark.png differ diff --git a/static/assets/images/database-discovery/postgres-app-components-light.png b/static/assets/images/database-discovery/postgres-app-components-light.png new file mode 100644 index 00000000..7999a9a3 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-app-components-light.png differ diff --git a/static/assets/images/database-discovery/postgres-discovery-credentials-dark.png b/static/assets/images/database-discovery/postgres-discovery-credentials-dark.png new file mode 100644 index 00000000..97df3135 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-discovery-credentials-dark.png differ diff --git a/static/assets/images/database-discovery/postgres-discovery-credentials-light.png b/static/assets/images/database-discovery/postgres-discovery-credentials-light.png new file mode 100644 index 00000000..fbbdd06c Binary files /dev/null and b/static/assets/images/database-discovery/postgres-discovery-credentials-light.png differ diff --git a/static/assets/images/database-discovery/postgres-job-dark.png b/static/assets/images/database-discovery/postgres-job-dark.png new file mode 100644 index 00000000..3411c4e1 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-job-dark.png differ diff --git a/static/assets/images/database-discovery/postgres-job-light.png b/static/assets/images/database-discovery/postgres-job-light.png new file mode 100644 index 00000000..0abf6d2a Binary files /dev/null and b/static/assets/images/database-discovery/postgres-job-light.png differ diff --git a/static/assets/images/database-discovery/postgres-on-prem-dark.png b/static/assets/images/database-discovery/postgres-on-prem-dark.png new file mode 100644 index 00000000..baa88d08 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-on-prem-dark.png differ diff --git a/static/assets/images/database-discovery/postgres-on-prem-light.png b/static/assets/images/database-discovery/postgres-on-prem-light.png new file mode 100644 index 00000000..ace7dca2 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-on-prem-light.png differ diff --git a/static/assets/images/database-discovery/postgres-run-now-dark.png b/static/assets/images/database-discovery/postgres-run-now-dark.png new file mode 100644 index 00000000..f31b4973 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-run-now-dark.png differ diff --git a/static/assets/images/database-discovery/postgres-run-now-light.png b/static/assets/images/database-discovery/postgres-run-now-light.png new file mode 100644 index 00000000..1ff08517 Binary files /dev/null and b/static/assets/images/database-discovery/postgres-run-now-light.png differ diff --git a/static/assets/images/database-discovery/resource-details-dark.png b/static/assets/images/database-discovery/resource-details-dark.png new file mode 100644 index 00000000..62113dc8 Binary files /dev/null and b/static/assets/images/database-discovery/resource-details-dark.png differ diff --git a/static/assets/images/database-discovery/resource-details-light.png b/static/assets/images/database-discovery/resource-details-light.png new file mode 100644 index 00000000..a6a35375 Binary files /dev/null and b/static/assets/images/database-discovery/resource-details-light.png differ diff --git a/static/assets/images/database-discovery/services-tab-dark.png b/static/assets/images/database-discovery/services-tab-dark.png new file mode 100644 index 00000000..d14f7ed8 Binary files /dev/null and b/static/assets/images/database-discovery/services-tab-dark.png differ diff --git a/static/assets/images/database-discovery/services-tab-light.png b/static/assets/images/database-discovery/services-tab-light.png new file mode 100644 index 00000000..f24b959a Binary files /dev/null and b/static/assets/images/database-discovery/services-tab-light.png differ diff --git a/static/assets/images/load-balancers/f5-resource-map-dark.png b/static/assets/images/load-balancers/f5-resource-map-dark.png new file mode 100644 index 00000000..b7a1215a Binary files /dev/null and b/static/assets/images/load-balancers/f5-resource-map-dark.png differ diff --git a/static/assets/images/load-balancers/f5-resource-map-light.png b/static/assets/images/load-balancers/f5-resource-map-light.png new file mode 100644 index 00000000..3ee998cb Binary files /dev/null and b/static/assets/images/load-balancers/f5-resource-map-light.png differ diff --git a/static/assets/images/load-balancers/load-balancer-details-dark.png b/static/assets/images/load-balancers/load-balancer-details-dark.png new file mode 100644 index 00000000..39141851 Binary files /dev/null and b/static/assets/images/load-balancers/load-balancer-details-dark.png differ diff --git a/static/assets/images/load-balancers/load-balancer-details-light.png b/static/assets/images/load-balancers/load-balancer-details-light.png new file mode 100644 index 00000000..cb232e54 Binary files /dev/null and b/static/assets/images/load-balancers/load-balancer-details-light.png differ diff --git a/static/assets/images/load-balancers/resources-f5-dark.png b/static/assets/images/load-balancers/resources-f5-dark.png new file mode 100644 index 00000000..b98e1e59 Binary files /dev/null and b/static/assets/images/load-balancers/resources-f5-dark.png differ diff --git a/static/assets/images/load-balancers/resources-f5-light.png b/static/assets/images/load-balancers/resources-f5-light.png new file mode 100644 index 00000000..1f593d60 Binary files /dev/null and b/static/assets/images/load-balancers/resources-f5-light.png differ