Skip to main content
Availability8.6.9 or later

What Is Monitored

Volume, errors, sign-in

How It Works

Query, logs, synthetic check

Deploy

Four monitors

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.

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.

Errors and Stuck Threads

Every error the InQuira servers log, by error code, with stuck threads reported separately.

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.

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

Analytics, Alerts and Automation

AI Analysis

Ask AI Explore questions such as “How did chat bot searches change this week?” Outlier detection flags a channel whose search volume drops or spikes. Error categorization 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 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

Oracle Knowledge Management Overview Dashboard - GermainUX

SLAs and Alerts

The sign-in check feeds the Synthetic Click and Synthetic Scenario KPIs, whose default SLAs flag a failed or slow sign-in. Add an SLA on Inquira Volume to hear about a channel whose searches stop. Get an alert by email, SMS, Slack or Teams when an SLA is breached.

Automation

When an SLA is breached, an automated action can run a diagnostic script, call an HTTP endpoint or open an incident.

How It Works

Data warehouse, logs, sign-in pageEngine monitorsKPIsAlerts
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 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

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

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

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

Troubleshooting

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.
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.
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.
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.
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.

KPIs

Synthetic Click and Synthetic Scenario are shared with other synthetic checks. See KPIs and SLAs.

Synthetic User Scenarios

How synthetic browser checks work

Query Monitoring

KPIs from database queries

File and Log Monitoring

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.

Contact GermainUX Support

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.

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.