Question
How do you find all Match Rules under the Sub-Optimal Match Rules Category?
Answer
To identify match rules that have been bypassed due to sub-optimal performance in Reltio, you can use the following API call:(community.reltio.com)
API Call:
GET {apiHost}/reltio/api/{tenant}/configuration/entityTypes/{entityType}/_skipMatchGroups
Response:
The response will be a JSON array listing the URIs of match rules that have been bypassed for the specified entity type. For example:
[ "configuration/entityTypes/HCP/matchGroups/Rule1", "configuration/entityTypes/HCP/matchGroups/Rule2" ]
If a match rule URI appears in this list, it indicates that the rule has been bypassed and does not participate in the matching process. Conversely, if a match rule is not listed, it is active and currently used in matching operations.
Understanding Bypassed Match Rules:
Reltio's Proactive Monitoring System continuously evaluates the performance of match rules. If a match rule is identified as causing performance issues—such as generating an excessive number of over-collision tokens—it may be automatically bypassed to maintain optimal system performance. These bypassed rules are considered "sub-optimal."(docs.reltio.com, community.reltio.com)
Re-enabling Bypassed Match Rules:
Administrators have the option to re-enable a bypassed match rule if necessary. This can be done through the Reltio Console or by updating the tenant's configuration. However, it's important to analyze the rule's performance impact before re-enabling it to ensure it doesn't adversely affect system operations.
References:
- Reltio Documentation on Sub-Optimal Match Rules
- Reltio Support Article on Finding Sub-Optimal Match Rules(support.reltio.com)
If you need assistance with analyzing or modifying match rules, feel free to ask.
Comments
Please sign in to leave a comment.