09:00Release Spring 2026 merged into master and went live · published to CDNYesterdayWorkflow Legal review approved by mkhanYesterdayjoesmith edited/summaryon spring-catalogMondayWorkflow Legal review assigned to mkhan
Full visibility into how content gets made
Audit every change, track workflow and contributor activity, and stream events to your BI and monitoring tools to find bottlenecks before they become problems.
Key features
-
Reports and alerts
Reports on workflow, jobs and activity, with alerts when a threshold is crossed.
-
Enterprise auditing
Every service call is recorded as JSON: who, what, which resource and when.
-
Event streams
Every change, merge and publish as an event your BI and monitoring tools can consume.
Reports and alerts
Reports are generated as your team works, so you can see how content moves through review and where it waits.
-
Reports
Report on workflows, the job queue, user activity and content, and chart metrics such as the most active contributors, content age and publishing throughput.
-
Workflow monitoring
Every workflow transition is tracked and timed, so statistics show what is working and where bottlenecks are.
-
Alerts
Send email, Amazon SNS or Slack notifications when a step takes too long or work falls behind schedule.
-
Export
Export reports to Excel, CSV or JSON for your own analysis tools.
Enterprise auditing for regulatory compliance
Log every interaction with the core system, down at the service level to record each principal, resource and method invocation (including arguments, the result, timing and system information) to produce a rich and detailed audit trail for use in regulatory compliance initiatives. The audit engine is available on dedicated Gitana Cloud and self-managed installations.
-
Audit trail
The audit engine captures every single method invocation within the service-layer of the Gitana Java data engine. Audit logs are written to disk as JSON, one record per call, with the principal, resource, method, arguments, result and timing.
-
Logging and S3 rollover
Audit logs are written with Log4j2, so they can be rotated and archived to cold storage, with built-in upload to Amazon S3 on rollover.
READ · NODEAudit record{
"_doc": "87d93692e40edaa9f1ba",
"action": "READ",
"principal": "joesmith",
"scope": "NODE",
"method": "read",
"handler": "nodeserviceimpl",
"args": [{
"type": "repository",
"value": {
"datastoreId": "21853c33f501377f49e6",
"datastoreTypeId": "repository",
"enableAuditing": true
}
}]
}
Event streams
Every interaction raises an event: content changes, branch merges, publishing. Events go to a message queue and an activities stream that your business intelligence and monitoring tools can consume as they happen.
-
Message queue
Events are placed on your configured queue in real time, for monitoring tools to transform and analyze.
-
Activities you can query
Query activity by user, branch, project, content item and time: what was modified, which branches merged, which release went live.
-
Tagged for your tools
Each event carries its project, user, content, branch and action, so you can feed it to Amazon Kinesis or a BI tool and correlate it with your CRM, marketing and support systems.
HamletActivitiesSee how Gitana fits your contentSee that merge around your own use case
In a demo, a solutions engineer walks you through Gitana around your use case.In a demo, a solutions engineer walks through a merge like this one around your use case. The same call covers architecture, security, deployment and procurement questions. In a guided evaluation, you work on your own content with one of our engineers on Gitana Cloud.