Talk to us

Guardian · MQ

Operational Intelligence for critical messaging.

IBM MQ on z/OS and Distributed. Service-aware, evidence-led, governed by policy and human authority.

01The Problem

MQ underpins the services that stop when it doesn't.

Payments. Core banking. Fraud detection. Customer channels. Batch. Data platforms. Every operational moment on MQ has a business moment behind it.

Critical messaging sits inside wider service chains. A queue building, a channel retrying, a message stuck in a dead-letter queue: none of these symptoms mean the fault domain is MQ. Blaming the loudest platform is the fastest way to a wasted midnight, an incident that repeats, and a post-mortem with no root cause. Guardian starts from the service, not the symptom.

02A Day on the Estate

A payment message fails.

Today

An alert fires. A qualified engineer reads the MQ reason code, analyses the message headers, determines the cause, assesses the service impact, identifies the corrective action, then executes remediation. Somewhere between the pager and the fix, the customer notices.

With Guardian

The failure is detected. The cause is classified. Business impact is assessed. A recommended action is generated. The decision is routed through the appropriate governance path. The engineer receives a diagnosis, not a raw alert.

03Service Context

Service chain, not silo.

Guardian holds the whole chain and correlates the evidence available at each hop. Investigation goes to the likely fault domain, not to the platform the alarm happened to fire on.

  1. Upstream systems
  2. Producer application
  3. MQ
  4. Network fabric
  5. MQ
  6. Consumer application
  7. Downstream systems

04Intelligence Foundation

The evidence Guardian uses.

Nothing is invented. Guardian correlates approved sources into an operational understanding that a qualified engineer can inspect.

  • Estate and configuration. Queue managers, queues, channels, definitions, dependencies.
  • Telemetry. PCF, MQ REST, statistics, accounting, events. On z/OS: SMF 115/116. On Distributed: platform mechanisms enabled by the client.
  • Incidents and RCA. Past incidents, root-cause records, resolutions that worked.
  • Change history. What was different yesterday, and who changed it.
  • Operational knowledge. The senior engineer's judgement, made durable.
  • Approved product intelligence. Datagentics's own model, disclosed at solution-architecture level.

05Decision + Action

Graded autonomy. Never uncontrolled.

Guardian never crosses the line from recommendation to action without permission you can defend. Two grades. One control plane. Every recommendation, approval, decision and action written to a complete operational audit trail.

Automatic

High-confidence, low-risk, reversible actions. Executed automatically within pre-approved policy, with notification. Guardian records exactly what it did and why.

Governed

Anything below the confidence threshold, or any higher-risk activity. Held for Qualified Human In The Loop approval before execution. Guardian never acts beyond its approved remit unattended.

06Verify + Learn

Every outcome strengthens the next.

Guardian verifies the outcome. Retains the evidence. Strengthens the Intelligence Foundation so tomorrow's diagnosis is faster, more confident, and easier to defend.

07Prototype Available Today

Real MQ. Real reason codes. Not slideware.

Guardian MQ is not a concept demo. The current prototype runs against real IBM MQ, and has been demonstrated on live infrastructure with real operational failure scenarios.

  • Real IBM MQ software. Not a simulation, not a mock.
  • Multiple queue managers. Live messaging channels between them.
  • Dead-letter queue processing. Real MQMD, real MQDLH, real MQ reason codes.
  • Real security-failure scenarios. Authority events differentiated from operational events.
  • Portable operational logic. Built on standard IBM MQ administrative interfaces. Ready to be repointed at enterprise estates, including IBM MQ on z/OS, without redesign.

Customer outcomes and validated case studies will appear as they become available. No invented percentages.

08Scope

What Guardian MQ is not.

  • Not a replacement for IBM MQ. Guardian sits alongside, complementing existing investment.
  • Not a replacement for monitoring. Guardian turns monitoring evidence into diagnosis and governed action.
  • Not a replacement for enterprise service management. Guardian integrates with ServiceNow and the workflows your organisation already runs.
  • Not uncontrolled automation. Every action Guardian takes sits inside approved policy and the Qualified Human In The Loop model.
  • Not a wholesale operational process change. Guardian is an intelligence layer, not a re-platforming project.

09How to Engage

Proposed next steps.

  1. 01Engineering Review SessionWalk through the current prototype and its operational reach.
  2. 02Architecture & Security AssessmentRead-only posture, deployment options, audit trail, integration points.
  3. 03Prototype DemonstrationLive scenarios against real MQ. Real reason codes, real remediation paths.
  4. 04Use Case ValidationMap the estate's real operational load onto Guardian's diagnostic model.
  5. 05Pilot EvaluationBounded, low-risk deployment. Measured operational value.

Resilience. Cost. Control.

MQ is not always the problem. Guardian knows the difference.