> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle Knowledge Management Monitoring

> Track knowledge search volume by channel, catch InQuira errors and stuck threads, and test the agent sign-in around the clock.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/deploy/germain-ux-js-profiler)
[`RPA Bot Recorder`](https://docs.germainux.com/deploy/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)

Availability
8.6.9 or later

> [card] [What Is Monitored](#what-is-monitored)
>
> Volume, errors, sign-in

> [card] [How It Works](#how-it-works)
>
> Query, logs, synthetic check

> [card] [Deploy](#deploy)
>
> Four monitors

> [card] [KPIs](#kpis)
>
> Volume and sign-in

## Overview

GermainUX shows how your Oracle Knowledge Management (formerly InQuira) deployment is used and whether it works. You see how many knowledge searches each channel made in the last 24 hours, the errors and stuck threads the InQuira servers log, and whether agents can sign in. A synthetic browser check signs in on a schedule, so a broken single sign-on page shows up before the first agent calls the help desk. Your team sees a drop in self-service searches, or a search server failing, as it happens.

> [card] Search Volume by Channel
>
> The number of searches in the last 24 hours for each source, such as web self-service, the agent desktop or a chat bot.

> [card] Errors and Stuck Threads
>
> Every error the InQuira servers log, by error code, with stuck threads reported separately.

> [card] Sign-In Tested Around the Clock
>
> A headless Chrome check signs in to Oracle Knowledge Management and records whether it worked and how long it took.

> [card] Console Logins
>
> Who signed in to the InQuira console, and when.

### Questions It Answers

* Did searches from web self-service drop today?
* Which channel makes the most knowledge searches?
* Which InQuira error codes are new, or happening more often?
* Are threads getting stuck on any server?
* Can agents sign in right now, and how long does it take?
* Who signed in to the InQuira console this week?

## What Is Monitored

| Area | What GermainUX monitors |
| - | - |
| **Search volume** | The number of searches in the last 24 hours for each query source, read from the InQuira data warehouse |
| **Errors** | Every log entry at level `Error`, named by its error code, with the full message. Messages that span several lines are joined. |
| **Stuck threads** | Error entries whose message starts with `[STUCK]`, reported apart from other errors |
| **Console logins** | Each console user login, with the user name and the server component from the log file name |
| **Sign-in** | A synthetic Chrome check that signs in through the single sign-on page and confirms the home page loads, with its duration and result |
| **Availability** | Up/down status and response time of the Oracle Knowledge Management URLs, with [synthetic HTTP checks](https://docs.germainux.com/automation/synthetic-http-execution.md) |
| **User experience** | Real-user page performance, JavaScript errors and Session Replay for agents and customers using the knowledge pages, with [RUM JS](https://docs.germainux.com/deploy/germain-ux-rum-js.md) or the [RUM Extension](https://docs.germainux.com/deploy/germain-ux-rum-extension.md) |
| **Host** | CPU, memory, disk and processes of the InQuira servers. See [Linux monitoring](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md) or [Windows monitoring](https://docs.germainux.com/integrations/windows-monitoring.md). |

## Analytics, Alerts and Automation

### AI Analysis

Ask [AI Explore](https://docs.germainux.com/analytics/ai-driven-insights.md) questions such as "How did chat bot searches change this week?" [Outlier detection](https://docs.germainux.com/analytics/outlier-detection.md) flags a channel whose search volume drops or spikes. [Error categorization](https://docs.germainux.com/analytics/data-categorization.md) groups similar error messages, so a new error stands out.

### Dashboards and Reports

The **Oracle Knowledge Management Overview** dashboard shows search volume by source, the duration of the sign-in check and its sign-in step, and failed sign-in checks. Build your own [dashboards and reports](https://docs.germainux.com/dashboards/dashboard-and-report.md) on errors by code and server, or any other KPI.

![Oracle Knowledge Management Overview dashboard with search volume by source, sign-in check duration, failed sign-in checks and sign-in step duration over a month](https://mintcdn.com/germain-ux/_BvaWMRonu1Uxv3M/images/main/oracle-knowledge-management-monitoring/oracle-km-overview-dashboard.png?fit=max\&auto=format\&n=_BvaWMRonu1Uxv3M\&q=85\&s=bc924b94785640b91b8658f37271de7c)

Oracle Knowledge Management Overview Dashboard - GermainUX

### SLAs and Alerts

The sign-in check feeds the **Synthetic Click** and **Synthetic Scenario** KPIs, whose default [SLAs](https://docs.germainux.com/analytics/slas.md) flag a failed or slow sign-in. Add an SLA on **Inquira Volume** to hear about a channel whose searches stop. Get an [alert](https://docs.germainux.com/automation/notifications.md) by email, SMS, Slack or Teams when an SLA is breached.

### Automation

When an SLA is breached, an [automated action](https://docs.germainux.com/automation/automated-actions.md) can run a diagnostic script, call an HTTP endpoint or open an incident.

## How It Works

Data warehouse, logs, sign-in page
Engine monitors
KPIs
Alerts

| Component | What it does |
| - | - |
| **Inquira Volume Monitor** | Runs a query on the InQuira data warehouse on a schedule. It counts the rows of `DW_STAGE.DW_STG_DATA` inserted in the last 24 hours, by `QUERY_SOURCE`, and stores one value for each source. |
| **InQuira Log Directory Monitor** | Watches the log directory for files named `Inquira*.log`, including numbered rotated files, and passes new lines to the parser |
| **InQuira Log Parser** | Reads each log entry, `<date> <level> <category> <code> <message>`, and turns errors, stuck threads and console logins into events |
| **Oracle KM Monitor - Chrome** | Opens the single sign-on page in headless Chrome on a schedule, signs in with the selected credentials, and checks that the home page shows its **Alerts** section. It records the sign-in as a synthetic transaction. |

All four run on a GermainUX Engine. The log monitor and parser need to read the InQuira log files, so they run on an Engine on the InQuira server or one that can read its log directory.

## Before You Start

* A [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md) can reach the InQuira data warehouse database and the Oracle Knowledge Management URL.
* A database account can read `DW_STAGE.DW_STG_DATA`.
* The Engine that runs the log monitor can read the InQuira log directory.
* Chrome is installed on the Engine that runs the sign-in check.
* An Oracle Knowledge Management account for the sign-in check, used for nothing else.

## Deploy

Each monitor has its own wizard. In the left menu, go to **Settings > Wizards** to find them. Deploy only the monitors you need.

### Search Volume

**1. Open the Database Query Monitor Deployment wizard**

On the **Database Query Monitor Deployment** card, click **Add**.

**2. Connect to the data warehouse**

On the **Database** step, select or create the InQuira data warehouse **Database** and its **Credentials**, and enter the **Monitored Software**, for example `Oracle Knowledge`. Click **Next**.

**3. Choose the component**

On the **Component** step, select **Inquira Volume Monitor**, and then click **Next**.

**4. Deploy it to the Engine**

On the **Deployment** step, enter a **Monitor Name**, select the **Monitoring Node** and Engine, and set the schedule. The default, `0 0 * * * *`, runs once an hour. Finish the wizard.

### Log Monitoring

**1. Deploy the parser**

On the **Parser Deployment** card, click **Add**. Select **InQuira Log Parser** as the **Component Type**, enter the **Monitored Application**, then on the **Deployment** step select the **Monitoring Node** and Engine, and finish the wizard.

**2. Deploy the log directory monitor**

On the **Directory Monitor Deployment** card, click **Add**. Select **InQuira Log Directory Monitor** as the **Component Type**, and enter the InQuira log **Directory**. On the **Deployment** step, select the same **Monitoring Node** and Engine as the parser, and finish the wizard.

GermainUX reads new lines as the InQuira servers write them.

### Synthetic Sign-In Check

**1. Open the Synthetic Web Component Deployment wizard**

On the **Synthetic Web Component Deployment** card, click **Add**.

**2. Enter the server and account**

On the **Server** step, select or create the **URI** of your Oracle Knowledge Management host, the **Credentials** of the check account, and the **Application Name**. Click **Next**.

![Synthetic Web Component Deployment wizard on the Server step, with the URI, Credentials and Application Name fields, and Inquira selected as the Application Name](https://mintcdn.com/germain-ux/H6IMBRdofVbwGIW3/images/main/oracle-knowledge-management-monitoring/synthetic-web-deployment-server-step.png?fit=max\&auto=format\&n=H6IMBRdofVbwGIW3\&q=85\&s=75c277e5039977d9ab44e637841d8e5b)

Synthetic Web Component Deployment Wizard, Server Step - GermainUX

**3. Choose the component**

On the **Component** step, select **Oracle KM Monitor - Chrome**, and then click **Next**.

**4. Deploy it to the Engine**

On the **Deployment** step, enter a **Monitor Name**, select the **Monitoring Node** and Engine, and set the schedule. The default runs once an hour. Use `0 */5 * * * *` to test the sign-in every 5 minutes. Finish the wizard.

The check signs in through your single sign-on page. If your sign-in page differs from the standard one, the GermainUX team adapts the check's script.

## Validate

**1. Check the search volume**

After the volume monitor's first run, open the **Inquira Volume** KPI. It shows one value for each query source.

![Inquira Volume KPI analysis showing the 24-hour search count over time and the count for each query source](https://mintcdn.com/germain-ux/H6IMBRdofVbwGIW3/images/main/oracle-knowledge-management-monitoring/inquira-volume-by-source.png?fit=max\&auto=format\&n=H6IMBRdofVbwGIW3\&q=85\&s=bef8a52c0d3bd382b9fef79ec5ef0866)

Search Volume by Source in the Inquira Volume KPI - GermainUX

**2. Check the sign-in**

After the sign-in check's first run, open the **Synthetic Scenario** KPI and filter on your Oracle Knowledge Management host. Each run shows its duration and whether it succeeded.

![Synthetic Scenario KPI analysis showing the maximum duration of the sign-in check over time, with the related Synthetic Click KPI](https://mintcdn.com/germain-ux/H6IMBRdofVbwGIW3/images/main/oracle-knowledge-management-monitoring/synthetic-scenario-analysis.png?fit=max\&auto=format\&n=H6IMBRdofVbwGIW3\&q=85\&s=4a1facc0bf13b680f50178c50acd480b)

Sign-In Check Duration in the Synthetic Scenario KPI - GermainUX

## Troubleshooting

> [accordion] Inquira Volume shows no data
>
> Check that the database account can run `select QUERY_SOURCE, COUNT(1) from DW_STAGE.DW_STG_DATA` in the data warehouse, and that the warehouse load is running. Rows without a `QUERY_SOURCE` aren't counted.

> [accordion] A channel's search volume falls to zero
>
> The count covers the last 24 hours of rows loaded into the warehouse. When the warehouse load stops, every channel drains toward zero. When only one channel drops, check the integration that sends its searches.

> [accordion] No log events appear
>
> Check that the Engine can read the log directory, that the log files are named `Inquira*.log` or `Inquira*.log1` and so on, and that the parser and the directory monitor are deployed on the same Engine.

> [accordion] The sign-in check always fails
>
> Check that the check account can sign in by hand, and that the Engine can reach the single sign-on page. If your sign-in page uses different field names, or the home page has no **Alerts** section, the script needs to be adapted to your pages.

> [accordion] The sign-in check fails to start
>
> Chrome must be installed on the Engine host, and the Engine must be able to start it headless.

## Security and Privacy

Oracle Knowledge Management monitoring data includes personal data:

* **Identity data**: the user names of console logins, and the user name of the sign-in check account
* **Screenshots and page content**: each sign-in check stores a screenshot and the HTML of the page it reached, which shows whatever that page displays to the check account
* **Free text**: InQuira error messages, which contain whatever the servers write into them. Treat them as possibly containing personal or customer data.

Use a dedicated check account that sees no customer data. To mask, anonymize or exclude this data, see [Data Privacy](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md).

## KPIs

| KPI | What it holds | Default SLA |
| - | - | - |
| **Inquira Volume** | Searches in the last 24 hours, one value for each query source | — |
| **Synthetic Click** | The sign-in step of each check, with its duration and result | OK below `5` seconds and successful, per host and step |
| **Synthetic Scenario** | Each complete check run, with its duration and result | OK below `15` seconds and successful, per host and scenario |

Synthetic Click and Synthetic Scenario are shared with other synthetic checks. See [KPIs](https://docs.germainux.com/analytics/kpis.md) and [SLAs](https://docs.germainux.com/analytics/slas.md).

## Related Documentation

> [card] [Synthetic User Scenarios](https://docs.germainux.com/automation/user-click-synthetic-user-scenario.md)
>
> How synthetic browser checks work

> [card] [Query Monitoring](https://docs.germainux.com/analytics/query-monitoring.md)
>
> KPIs from database queries

> [card] [File and Log Monitoring](https://docs.germainux.com/integrations/file-log-monitoring.md)
>
> How GermainUX reads log files

## Get Help

The GermainUX team can adapt the sign-in check to your single sign-on page, and add queries for other data warehouse figures.

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.