Jarsis IBM TRIRIGA Insights
Know what's breaking before your users do.
Continuous monitoring, automated diagnosis, and validated fix suggestions across your TRIRIGA environments, powered by TRIRIGA's own APIs and AI.
The problem
Large TRIRIGA operations run blind across environments.
Dev, SIT, UAT, AMS, production. Each with multiple servers. After months of deployments, patches, and hotfixes, drift creeps in and nobody can see it.
Nobody knows if environments are consistent
Are the same workflows published everywhere? Same versions? Same business object fields? Same form configurations?
Server logs don't speak in fixes
TRIRIGA writes errors as Java stack traces. Useful to compilers, opaque to humans. Even with 20+ years on the platform, translating "NullPointerException at workflow step 3" into "that step assumed a field was populated and needs a guard" takes hours of manual investigation. Most errors sit unread until users complain.
Regressions reappear silently
A bug fixed in Sprint 42 comes back in Sprint 48. Nobody notices for weeks.
Promotion validation doesn't exist
After a release migrates from Dev to SIT to UAT, how do you know it applied correctly? You don't, until something breaks.
How it works
The same lightweight servlet, on every server, in every environment.
An AWS-hosted intelligence engine connects to all of them. It will continuously:
Scan server logs
On a configurable schedule, across every server (UI and process servers).
Snapshot metadata
Periodic snapshots of workflows, business objects, fields, forms, associations.
Compare environments
Detect drift in workflow versions, BO configurations, list values.
Diagnose errors automatically
Not just log parsing. Active investigation using TRIRIGA's own Java APIs.
The cycle
Detect → Validate → Suggest.
When an error appears in a server log, Jarsis won't just alert. It will investigate. Raw stack traces become corrective fixes: what the workflow assumed, what was missing, and what should have guarded against it.
Error in server.log
NullPointerException in triApprovalGate step 3, record 894521
Using TRIRIGA's own APIs:
- → Pull the record. Status “In Progress”
- → Step 3 reads triAssignedToCN. NULL
- → Field is required, not enforced on form
- → 6/7 environments have a validation workflow that prevents this
- → Dry-run the fix. Would work
Root cause + fix:
This environment is missing workflow triAssignmentValidation (deployed on 6 other environments). Publish it here. 3 other records have the same issue.
Sent to the team:
Slack, Teams, or email. Full diagnosis with the suggested fix attached.
Alerting integrations are planned.
Your team's job becomes verify and apply, not investigate.
Drift detection
Continuous comparison across all your environments.
Designed to detect:
Workflow matrix
Which version of each workflow is on each environment.
Business object diff
Missing fields, changed required/read-only flags, form layout differences.
List value drift
Classification lists with different values across environments.
Promotion readiness
"Is SIT ready to promote to UAT? No: triEscalationTimer failed to migrate."
Complementary to IBM Instana
Not an APM. A TRIRIGA-native diagnostic layer.
Jarsis Insights doesn't replace Instana or any existing infrastructure monitoring. Instana tells you something broke. Jarsis tells you what broke in TRIRIGA terms (which workflow, which field, which business object), and how to fix it.
Sees
Instana
Java exceptions, HTTP errors, JVM metrics
Jarsis Insights
TRIRIGA workflows, BOs, fields, forms, metadata
Tells you
Instana
"NullPointerException at 09:14"
Jarsis Insights
"Workflow triApprovalGate step 3 fails because triAssignedToCN is NULL. This field was renamed."
Fix guidance
Instana
None
Jarsis Insights
"Publish triAssignmentValidation to this environment. 3 records affected."
Scope
Instana
Any Java app
Jarsis Insights
TRIRIGA-specific. Understands the platform
What it will cost
One virtual TRIRIGA specialist.
£28,000 / month
50% off during 3-month PoCFor up to 10 TRIRIGA applications (all servers per application monitored).
Pricing applies once Insights is generally available. Early access participants get preferential terms.
Join the early access programme.
Shape the product
Tell us which environments, drift patterns, and alerts matter most to your team.
Get early access
Be among the first to run cross-environment metadata comparison and automated diagnosis.
See a preview
We'll walk through the architecture and the Detect → Validate → Suggest cycle on your data.