Keymate Logo

Catch Every Event Error—Before It Becomes a Problem

Keymate captures and classifies every failure during event transformation with structured logs at INFO, WARN, and ERROR levels—empowering operations, compliance, and developers to act fast, fix confidently, and audit precisely.

Monitor and Classify Every Transformation Failure with Precision

From Parse Failures to Schema Violations—It's All Logged

Every incoming or outgoing event in Keymate passes through one or more transformation layers, whether for: JSON to Protobuf mapping. Field renaming and enrichment. Payload restructuring. Schema validation. Metadata mapping (e.g., source ID to internal object ID). Keymate logs every anomaly with: Log level (INFO, WARN, ERROR). Failed field(s), payload snapshot. Initiating user (if traceable), org context. Transformation step name and module. Trace/session ID for root cause mapping. Kafka topic and partition metadata. Optional fix recommendations (diff hints).

Transformation Error Logging & Alerting

Comprehensive error logging system that captures every transformation failure with structured logs for operations, compliance, and development teams.

Example: Monitor and classify every transformation failure with precision

Key Components:

Multi-Level Error Logging
Transformation-Aware Context
Kafka Metadata Logging
Anomaly Detection
Tenant Attribution

What Makes It Unique

Multi-Level Error Logging

Logs at INFO, WARN, ERROR with clear boundaries and severities

Transformation-Aware Context

Logs include which enrichment rule or field mapping failed

Structured, Queryable Format

JSON logs consumable by SigNoz, Kafka, Elasticsearch

Kafka-Aware Metadata Logging

Includes topic, offset, partition, and correlation ID

Anomaly Detection Compatible

Feeds into alert systems to detect systematic errors

Keycloak-Extended Logging

Adds deep event-level logging even within Keycloak's limited default scope

Per-Event Feedback Loop

Optional return messages or dead-letter queue publishing for unrecoverables

Tenant & Org Unit Attribution

Supports per-tenant filtering and compliance-level isolation

Frequently Asked Questions

All transformation pipelines: including Event Hub, OpenMetadata mappers, format converters, and field normalizers.
INFO: successful transformation with optional non-critical notes. WARN: incomplete mapping or recoverable issues. ERROR: validation failures, schema mismatches, critical enrich failures.
Yes. ERROR-level logs can be routed to Dead Letter Topics, Slack alerts, or compliance vaults.
Yes. We've extended Keycloak to emit internal events (e.g., user update, role assignment) with transformation-aware logging where applicable.
Yes. All logs include tenant, org-unit, and optionally session/user identity.

How to Use This Feature

Follow these steps to enable comprehensive transformation error logging.

Implementation Steps

1

Enable transformation logging module in Admin Console

2

Configure severity thresholds and destinations (SigNoz, Elastic, Kafka, S3)

3

Define alert rules for ERRORs in critical flows

4

Use filters in observability UI to locate schema/format errors

5

Enable auto-degradation to warn level if downstream tolerant

6

Monitor fix suggestions to adjust transformation rules over time

ELEVATE YOUR IAM STRATEGY

Ready to Transform Your Keycloak Experience?

Implement fine-grained authorization, multi-tenant infrastructure, and comprehensive security policies with Keymate — built on the Keycloak foundation you already trust.