Study guide

14.1 Business Events: Capture, Ingestion & the bizevents Grail Table

Dynatrace Certified Associate Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Overview, Deployment Models & Architecture

1.1 Dynatrace Platform Capabilities, Web UI Navigation & the Dynatrace Hub 1.2 SaaS vs. Dynatrace Managed Architecture & Security 1.3 Core Telemetry Components: OneAgent, ActiveGate & Grail Lakehouse 1.4 Licensing Models: Dynatrace Platform Subscription (DPS) & Davis Data Units (DDUs)

2 Chapter 2: ActiveGate Architecture & Network Topologies

2.1 ActiveGate Types: Environment vs. Cluster ActiveGates 2.2 ActiveGate Capabilities: Proxying, Private Synthetic, Cloud Integrations & Extensions 2.3 Network Zones, Multi-DC Routing & Firewall Traversal

3 Chapter 3: OneAgent Deployment, Configuration & Management

3.1 OneAgent Architecture, Components & Automatic Injection 3.2 Host Installation on Linux, Windows & Containerized Hosts 3.3 Cloud-Native Deployment: Dynatrace Operator on Kubernetes & OpenShift 3.4 Kubernetes Observability: Clusters, Nodes, Namespaces, Workloads & Events

4 Chapter 4: Monitoring Modes, Process Groups & Infrastructure Observability

4.1 Monitoring Modes: Full-Stack vs. Infrastructure-Only vs. Discovery 4.2 Process Groups, Process Instances & Custom Process Group Detection Rules 4.3 Host Groups, Host Naming Rules & Environmental Metadata Extraction 4.4 Infrastructure & Operations: Host Health, Disk, Network & Availability Analysis 4.5 Database Observability: The Databases App, Connection Pools & Storage Latency

5 Chapter 5: Smartscape Topology & Service Flow

5.1 The 5-Layer Smartscape Topology: Datacenter to Application 5.2 Service Detection: Web Services, Background Tasks & Custom Services 5.3 Service Flow, Backtrace Analysis & Horizontal/Vertical Dependency Mapping

6 Chapter 6: PurePath Distributed Tracing & Code-Level Diagnostics

6.1 PurePath Architecture, Distributed Tracing & Request Context Propagation 6.2 Method Hotspots, CPU Profiling & Memory Allocation Thread Analysis 6.3 Database Service Diagnostics, Slow Queries & Exception Analysis

7 Chapter 7: Davis AI Engine, Baselining & Causation

7.1 Davis Deterministic Causation Engine vs. Pure Correlation 7.2 Automated Dynamic Baselining, Percentiles & Traffic Seasonality 7.3 Event Ingestion, Event Types & Event Hierarchy in Problem Evolution

8 Chapter 8: Problem Lifecycle, Root Cause Analysis & Alerting

8.1 Problem Lifecycle, Severity Categories & Root Cause Cards 8.2 Alerting Profiles, Delay Filters & Management Zone Routing 8.3 Problem Notification Integrations: Webhooks, Slack, ServiceNow & ITSM

9 Chapter 9: Digital Experience Monitoring: Synthetic Monitoring

9.1 Synthetic Monitors: HTTP, Single-Step Browser & Multi-Step Clickpaths 9.2 Private Synthetic Locations, ActiveGate Engines & Credential Vault 9.3 Outage Detection, Performance Baselining & Maintenance Suppression

10 Chapter 10: Digital Experience Monitoring: Real User Monitoring (RUM)

10.1 RUM Architecture, OneAgent Script Injection & Mobile/OpenKit Telemetry 10.2 User Actions: Load vs. XHR/Fetch Actions, Visually Complete & Speed Index 10.3 Apdex Performance Ratings, User Sessions & Session Replay Masking

11 Chapter 11: Log Management and Analytics on Grail with DQL

11.1 Log Management on Grail: Storage, Ingestion Pipelines & Log Masking 11.2 Dynatrace Query Language (DQL): Fetch, Filter, Fields & String Operations 11.3 DQL Aggregations: Summarize, MakeTimeseries, Sorting & Visualizations

12 Chapter 12: Platform Governance, OpenTelemetry & Automation

12.1 Management Zones: Scoping Observability, Dashboards & Access Control 12.2 Tagging Strategies: Automated Rule-Based Tags, Manual Tags & AWS/K8s Metadata 12.3 OpenTelemetry Ingestion, OpenPipeline & Dynatrace Workflows Automation

13 Chapter 13: Cloud Integrations & Agentless Infrastructure Ingestion

13.1 AWS, Azure & Google Cloud Integrations 13.2 VMware vSphere, Extensions & Other Agentless Ingestion Paths

14 Chapter 14: Business Analytics & Business Events

14.1 Business Events: Capture, Ingestion & the bizevents Grail Table 14.2 Business Analytics: Connecting Performance to Revenue, Conversion & KPIs

15 Chapter 15: Notebooks, Dashboards & Data Visualization

15.1 Notebooks: Section-Based Investigation & Shareable Analysis 15.2 Dashboards: Tiles, Variables, Segments & Continuous Monitoring 15.3 Choosing Visualizations: Data Explorer, Chart Types & Metric Selection

16 Chapter 16: Reporting, Metrics & User Behavior Analysis

16.1 Metrics on Grail: Built-in Metrics, Granularity & Retention 16.2 Dashboard Reports, Subscriptions & Exporting Data via APIs 16.3 User Behavior Analysis: Bounce Rate, Landing & Exit Pages, Conversion Goals 16.4 Session Segmentation, User Journeys & Funnel Drop-Off Analysis

17 Chapter 17: Security, Vulnerability Analytics & Application Protection

17.1 Platform Security: Data Privacy, Encryption & Access Control 17.2 Third-Party Vulnerabilities, the Davis Security Score & Security Advisor 17.3 Code-Level Vulnerabilities, Attacks & Runtime Application Protection 17.4 Security Investigator, Notifications & the Remediation Workflow

14.1 Business Events: Capture, Ingestion & the bizevents Grail Table

Key Takeaways Explain This Topic AI

Business Analytics is one of the twelve scored Associate exam topics, and business events are the data type that powers it.

Business events reach Grail from four sources: OneAgent capture rules on incoming HTTP requests, RUM data, the business events ingest API, and logs.

OneAgent capture rules extract business events from specific web services or endpoints without any application code change.

The dedicated ingest endpoint is /api/v2/bizevents/ingest, which accepts JSON records from external systems.

Business events land in the bizevents table in Grail and are queried with the same DQL used for logs and spans, starting with 'fetch bizevents'.

Last updated: September 2026

Every signal covered so far answers a technical question: how fast, how many, how healthy. Business events answer a different one: what happened to the business? An order was placed for £248.50. An insurance quote was abandoned at step 3. A payment was declined by the issuer.

Business Analytics is a separately scored topic on the Associate exam score report, and the official learning path devotes half of its Business Analytics & DEM lesson to business events. Dynatrace's own framing is that Business Analytics connects application performance and user experience to business metrics, enabling business and IT teams to collaborate through shared real-time perspectives, and it leverages business events to achieve the precision many business use cases demand.

What Makes a Business Event Different

  • Property Metric Log line Business event
  • Shape Numeric time series Unstructured or semi-structured text Structured record with typed fields
  • Granularity Aggregated Per emission Per business occurrence
  • Precision Sampled/aggregated Depends on log level Not sampled — every occurrence

Typical question "What is the average latency?" "What error was thrown?" "How much revenue did that outage cost?"

The precision point is the one exam questions lean on. Traces may be sampled by Adaptive Traffic Management; business events are not , because a financial or compliance record that is 90% accurate is worthless. If a scenario says "we need an exact count of completed transactions," the answer is business events, not a request-count metric.

The Four Sources of Business Events

Business events can come from OneAgent (stored in the bizevents Grail table), RUM data , generic data ingest via the bizevents API endpoint , and logs .

1. OneAgent capture rules — the zero-code path

OneAgent can capture business events from incoming HTTP requests using capture rules that tell OneAgent to capture business events when specific web services or endpoints are called. A rule specifies:

  • Trigger — which endpoint, path, or web service the rule applies to (for example POST /api/v1/orders )
  • Event type and provider — how the record is classified

Field extraction — which values to pull from the request or response body, headers, query parameters, or path segments

Because the extraction happens inside the already-injected agent, no application code changes and no redeployment are required . This is the exam's favourite business-events fact: a team that wants order-value analytics on an existing, unchanged production service can have it by configuring a capture rule.

2. RUM

Browser and mobile RUM instrumentation can emit business events from the client side, which is how front-end funnel steps and abandonment points that never reach a backend endpoint get captured.

3. The business events ingest API

For systems Dynatrace does not instrument — a mainframe, a partner settlement feed, an ERP export — Business Observability offers the Business events API to ingest JSON-format data via the /bizevents/ingest endpoint: POST https://{environment-id}.live.dynatrace.com/api/v2/bizevents/ingest

Content-Type: application/json

  • {
  • "event.provider": "erp.settlement",
  • "event.type": "payment.settled",
  • "order.id": "A-99213",
  • "payment.amount": 248.50,
  • "payment.currency": "GBP",
  • "customer.tier": "gold"
  • }
  • 4. Logs

Where an application already writes a structured line containing the business fact, that line can be transformed into a business event on ingest rather than duplicating the emission.

Where They Live and How You Read Them

Business events are stored in the bizevents table in Grail and are queried with the same DQL used for logs, spans, and metrics. The learning path's own call to action is to run: fetch bizevents

  • …and inspect what comes back. Building on the DQL taught in Chapter 11: fetch bizevents, from: now() - 24h
  • | filter event.type == "order.completed"
  • | summarize revenue = sum(order.amount),
  • orders = count(),
  • by: { customer.tier }
  • | sort revenue desc

One query, no separate BI tool, no nightly export — and because it is the same Grail store, the same timeframe filter can be applied to the problem that was open during that window.

Modelling Rules That Matter

Use a consistent event.provider and event.type taxonomy. These are the primary grouping dimensions; inconsistent naming makes the data unqueryable in practice.

Type your numeric fields as numbers , not strings — sum() and avg() cannot aggregate a string.

Do not put personally identifiable information in business events unless your data-protection posture explicitly allows it. Masking on ingest is covered in Chapters 10 and 11 and applies here too.

Business events are metered. Ingest what the business will actually query rather than everything the application knows.

Choosing the Right Source

  • Situation Correct source
  • Existing instrumented service, no code change allowed OneAgent capture rule
  • Front-end funnel step that never hits the backend RUM
  • External or uninstrumentable system Business events ingest API
  • Fact already present in a structured log line Logs

Loading diagram... The Four Paths a Business Event Takes into Grail