Benefits
Business value of query KPIs
Measures and pivots
Choose values and dimensions
Create a KPI for a query
From query to KPI
Deployment and configuration
Set up query-based insights
SQL Query-Based Insights
SQL Query-Based Insights enable GermainUX to periodically execute a customer-defined SQL query and turn the returned data into real-time business or technical KPIs. Use this capability when the insight you need is stored in a database but is not available through another GermainUX data source.Overview
For example, GermainUX can query a database to monitor:
The query results become GermainUX facts that can be analyzed using KPIs, measures, pivots, SLAs, rules, dashboards, alerts, reports, and approved automated actions.
Benefits
SQL Query-Based Insights help organizations:- Convert database records into actionable real-time insights.
- Monitor business conditions that are not exposed through application telemetry.
- Detect failed, delayed, incomplete, or unusual transactions.
- Measure business-process volume, performance, and backlog.
- Identify data-quality and operational issues.
- Analyze database-derived insights alongside user-experience, application, infrastructure, and integration data.
- Notify responsible teams when an important condition is detected.
- Initiate approved diagnostic or corrective actions.
How it works
1
The GermainUX Engine connects to an authorized database
2
It executes a configured SQL query at the defined interval
3
The returned data is mapped to a GermainUX KPI
4
GermainUX stores and analyzes the resulting facts
5
Rules, SLAs, dashboards, alerts, reports, or automation can use the insight
Examples
Query results and KPIs
Each query is associated with a GermainUX KPI that defines how its results are stored and analyzed. Depending on the use case, the KPI can represent:
A query can use an existing KPI or a customer-defined KPI.
See Custom Insights and KPIs, Pivots & Measures.
Measures and pivots
The columns returned by a query can provide values and dimensions for analyzing the resulting KPI. Measures can include:- Record count
- Transaction duration
- Processing delay
- Backlog size
- Transaction value
- Error count
- Completion rate
- Customer-specific numeric values
- Application
- Environment
- Database
- Business process
- Transaction type
- Status
Show all 11
Show all 11
- Error type
- Customer
- Product
- Region
- Assigned team
Overdue Service Request KPI could be measured by count and processing delay, then segmented by priority, assigned team, request type, and region.
Rules and SLAs
Apply GermainUX rules to categorize, enrich, filter, or correlate the facts generated by a query. Examples include:- Categorize failures using a returned error code.
- Assign a severity according to transaction value.
- Associate a database record with a business process.
- Detect when the result exceeds a defined threshold.
- Correlate the result with related application or integration activity.
- Number of matching records
- Transaction age
- Processing duration
- Backlog size
- Business value
- Time since the last successful update
Configure a Query Monitor
Prerequisites
Before configuring the monitor, ensure that:- A GermainUX Engine can connect to the database.
- The database type is supported and its driver is available.
- Authorized database credentials are configured.
- Network and firewall access are available.
- The SQL query has been tested.
- The database account has access only to the required data.
- The corresponding GermainUX KPI exists or can be created.
Create a Query Monitor component
- Sign in to the GermainUX Workspace.
- Go to System > Component Types.
- Add a Database Query Monitor Component.
- Enter a name for the component.
- Select the database connection.
- Select the authorized database credentials.
- Enter a descriptive name for the query.
- Enter and validate the SQL query.
- Select the GermainUX KPI that will receive the results.
- Configure a custom rule when returned values require mapping or transformation.
- Configure the execution interval and other available settings.
- Add an SLA when the result must be evaluated against a threshold.
- Save the component.
- Confirm that the Engine executes the query and that the resulting facts appear under the selected KPI.
Add a query to an existing component
- Go to System > Component Types.
- Open the existing Database Query Monitor component.
- In the Queries section, select Add.
- Select the database connection and credentials.
- Enter a name for the query.
- Enter and validate the SQL statement.
- Select the destination KPI.
- Configure a custom rule when required.
- Save the query.
Create a KPI for a query
1
Go to Analytics > KPIs
2
Select Add
3
Enter a clear KPI name
4
Select the appropriate fact class, such as Generic Event or Generic Transaction
5
Enter a unique fact category, such as Query: Overdue Service Requests
6
Configure the relevant measures and pivots
7
Add an SLA when required
8
Configure relationships, rules, alerts, or automation as needed
9
Save the KPI
10
Select the KPI in the Query Monitor configuration
Analyze query-based insights
After data collection begins, use GermainUX to:- Measure the frequency and business impact of the detected condition.
- Analyze historical trends.
- Segment results using KPI pivots.
- Compare environments or periods.
- Identify abnormal volumes or durations.
- Correlate database findings with user, application, API, integration, or infrastructure activity.
- Drill down to individual database-derived facts.
- Apply alerts, Watches, reports, or approved automated actions.
Security and performance
Queries execute against customer databases and should follow the organization’s database-security and operational-governance requirements. Recommended practices include:- Use a dedicated database account.
- Grant only the permissions required by the configured queries.
- Prefer read-only access.
- Avoid collecting sensitive data unless it is required and authorized.
- Select only the columns needed for the insight.
- Filter results as narrowly as possible.
Show all 12
Show all 12
- Avoid unbounded or unnecessarily expensive queries.
- Use indexed columns when filtering large tables.
- Configure an execution interval appropriate for the business need.
- Test queries outside production before enabling them.
- Monitor the query’s execution time and database impact.
- Review retention and access requirements for the collected results.
Troubleshooting
If no facts are generated:1
Confirm that the GermainUX Engine is running
2
Verify network access from the Engine to the database
3
Validate the database connection and credentials
4
Execute the SQL query using an authorized database client
5
Confirm that the query returns the expected columns and values
6
Verify that the query is enabled
7
Confirm that the destination KPI and fact category are correct
8
Review Engine logs for connection, SQL, mapping, or processing errors
9
Confirm that the selected time range and filters include the generated facts
Deployment and configuration
- Deploy and configure the GermainUX Engine.
- Configure an authorized connection to the target database.
- Create or select a KPI for the query results.
- Configure rules through Rules: Advanced Automated Analytics when results require filtering, categorization, enrichment, or correlation.
- Configure SLAs when the resulting insight must be evaluated against a threshold.
- Add dashboards, alerts, Watches, reports, or approved actions according to the operational requirement.
Get Help
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.