Dynatrace · Schema
LogIngestRecord
A single log record to ingest into the Dynatrace Grail data lakehouse. The content field is required. Additional fields provide context for routing, filtering, and entity association.
AI OperationsAnalyticsAPMApplication Performance MonitoringApplication SecurityAutomationCloud MonitoringDigital Experience ManagementIntelligenceObservability
Properties
| Name | Type | Description |
|---|---|---|
| content | string | The main log message or text. Required. This is the primary searchable content of the log record. |
| severity | string | The severity level of the log record. Standard syslog severity levels are supported. |
| timestamp | string | The timestamp of the log record. Accepts ISO 8601 format (e.g., 2024-01-15T10:30:00.000Z) or Unix timestamp in milliseconds. If not specified, the ingestion time is used. |
| log.source | string | A string identifier for the source of the log record, such as an application name, component, or log file path. |
| dt.entity.host | string | The Dynatrace host entity ID to associate this log record with, e.g., HOST-1234567890ABCDEF. This enables correlation between logs and monitored infrastructure. |
JSON Schema
{
"type": "object",
"description": "A single log record to ingest into the Dynatrace Grail data lakehouse. The content field is required. Additional fields provide context for routing, filtering, and entity association.",
"properties": {
"content": {
"type": "string",
"description": "The main log message or text. Required. This is the primary searchable content of the log record.",
"example": "example-value"
},
"severity": {
"type": "string",
"description": "The severity level of the log record. Standard syslog severity levels are supported.",
"example": "EMERGENCY",
"enum": [
"EMERGENCY",
"ALERT",
"CRITICAL",
"ERROR",
"WARNING",
"NOTICE",
"INFO",
"DEBUG",
"TRACE"
]
},
"timestamp": {
"type": "string",
"description": "The timestamp of the log record. Accepts ISO 8601 format (e.g., 2024-01-15T10:30:00.000Z) or Unix timestamp in milliseconds. If not specified, the ingestion time is used.",
"example": "example-value"
},
"log.source": {
"type": "string",
"description": "A string identifier for the source of the log record, such as an application name, component, or log file path.",
"example": "example-value"
},
"dt.entity.host": {
"type": "string",
"description": "The Dynatrace host entity ID to associate this log record with, e.g., HOST-1234567890ABCDEF. This enables correlation between logs and monitored infrastructure.",
"example": "example-value"
}
},
"required": [
"content"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "LogIngestRecord"
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/dynatrace-log-monitoring-v2-log-ingest-record"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.