builtin:logmonitoring.timestamp-configuration)
Dynatrace OneAgent detects number of timestamp formats in your log records. In case of custom timestamps included in log record define them below. This will assure data quality for analysis. Timestamp detection also influence proper log splitting. If no timestamp is detected or log format prevents auto-timestamping, adjacent lines can be merged into single log record (also indentations are considered).
builtin:logmonitoring.timestamp-configuration
group:log-monitoring
group:log-monitoring.ingest-and-processing
HOST
- HostKUBERNETES_CLUSTER
- Kubernetes clusterHOST_GROUP
- Host Groupenvironment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:logmonitoring.timestamp-configuration |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:logmonitoring.timestamp-configuration | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:logmonitoring.timestamp-configuration |
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
enabled
config-item-title
date-time-pattern
timezone
date-search-limit
Defines the number of characters in every log line (starting from the first character in the line) where the timestamp is searched.
entry-boundary
Optional field. Enter a fragment of the line text that starts the entry. No support for wildcards - the text is treated literally.
Matcher
objectattribute
dt.entity.process_group
log.source
log.source.origin
host.tag
k8s.container.name
k8s.namespace.name
k8s.deployment.name
k8s.pod.annotation
k8s.pod.label
k8s.workload.name
k8s.workload.kind
container.name
dt.entity.container_group
process.technology
operator
MATCHES
values
EntryBoundary
objectpattern