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

# Configure Categorization

> Categorization is preconfigured for many applications built with standard technologies, including Java, Go, PHP, JavaScript, and C++.

Service
`Analytics`

Availability
2015.1 or later

> [card] [Overview](#categorization-overview)
>
> Preconfigured for common stacks

> [card] [Access](#access-categorization)
>
> Create and test definitions

> [card] [Technology Setup](#technology-specific-configuration)
>
> Setup by application technology

> [card] [Validate](#validate-categorization)
>
> Test logic on historical data

> [!NOTE]
>
> GermainUX Categorization automatically groups similar errors, exceptions, crashes, and other events. This helps teams separate known issues from newly detected ones, reduce duplicate noise, and prioritize the problems that require investigation.

## Categorization overview

Categorization is preconfigured for many applications built with standard technologies, including Java, Go, PHP, JavaScript, and C++.

### When custom categorization may be required

* An application generates complex or application-specific errors.
* Similar exceptions contain dynamic values that prevent direct matching.
* A crash must be identified using multiple attributes.
* Categorization requires data from multiple sources.
* The default category identifier needs a clearer business label.

Custom logic can be implemented through a JavaScript processor.

## Access Categorization

Go to:

**Germain Workspace > Settings > Analytics > Categorization**

![Categorization View](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-categorization/image-20260825-032338.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=5dedca132d90f8ab4b1f83f6de48b27e)

Categorization View - GermainUX

From this view, you can create, update, test, and manage categorization definitions.

## Technology-Specific Configuration

### Java Exceptions

Java exception categorization is generally available out of the box. Custom processing can be added for application-specific exception structures or naming requirements.

For assistance, [contact GermainUX](https://docs.germainux.com/main/support.md).

### JavaScript Errors

Errors captured by RUM JS or the RUM Browser Extension can be categorized using their message, stack trace, source, application, page, and other available attributes.

For assistance with custom JavaScript error categorization, [contact GermainUX](https://docs.germainux.com/main/support.md).

### Salesforce Apex Exceptions

See [Configure Salesforce Apex Exception Categorization](https://docs.germainux.com/main/apex-exception-monitoring-for-salesforce-cloud-con.md).

### Oracle Siebel Object Manager Crashes

See [Configure Siebel Object Manager Crash Categorization](https://docs.germainux.com/main/siebel-crash-monitoring-configuration.md).

## Assign Human-Readable Category Labels

GermainUX automatically generates category IDs for identified groups of similar events. You can assign human-readable labels to these categories so users can understand and analyze them more easily.

For example, a generated category ID can be labeled as:

* Checkout payment failure
* Salesforce Apex governor-limit exception
* Siebel Object Manager crash
* JavaScript error in product search
* Authentication service timeout

![Categorization Label](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-categorization/image-20260825-032742.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=94bd646a5e5feeb6c15de38cb19b75c2)

Categorization Label - GermainUX

Human-readable labels improve dashboards, reports, alerts, filters, and error analysis without changing the underlying category logic.

## Validate Categorization

GermainUX includes a tester that applies the selected categorization logic to historical data before it is used for real-time analysis.

To validate a categorization:

1. Open **Germain Workspace > Settings > Analytics > Categorization**.
2. Select the categorization definition you want to test.
3. Select the historical time range to analyze.
4. Click the **Play** button in the right-side panel.

   ![Validate Categorization](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-categorization/image-20260825-032437.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=e7ea698843b489c5b76c0cc30a4a64d6)

   Validate Categorization - GermainUX
5. Review the events grouped under each identified category.
6. Refine the processor or labels if the results are too broad, too narrow, or unclear.
7. Repeat the test until the results accurately represent the issues you want to identify.

Testing against historical data helps confirm that the categorization logic produces meaningful results before it processes new events in real time.

## Additional Resources

> [card] [Troubleshoot GermainUX](https://docs.germainux.com/main/germain-enterprise-troubleshooting.md)
>
> Read more

> [card] [Management](https://docs.germainux.com/main/management.md)
>
> More Management Features

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/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.