builtin:logmonitoring.log-storage-settings)You can include and exclude specific log sources for analysis by Dynatrace Log Monitoring. The ingest of log records is based on below rules that use matchers like log path, log levels, process groups, k8s specific selectors and more.
To ingest logs, create a new ingest rule. Use suggestions or type in the log source. You can review available log sources on the Process Group Instance screens. You need to define a custom log source if the required log source is not listed.
builtin:logmonitoring.log-storage-settingsgroup:log-monitoringgroup:log-monitoring.ingest-and-processingHOST - HostKUBERNETES_CLUSTER - Kubernetes clusterHOST_GROUP - Host Groupenvironment| GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:logmonitoring.log-storage-settings |
| SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:logmonitoring.log-storage-settings | |
| Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:logmonitoring.log-storage-settings |
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.
enabledconfig-item-titlesend-to-storageIf true matching logs will be included in storage. If false matching logs will be excluded from storage.
Matcher objectattributedt.entity.process_grouplog.sourcelog.source.originlog.contentloglevelhost.tagk8s.container.namek8s.namespace.namek8s.deployment.namek8s.pod.annotationk8s.pod.labelk8s.workload.namek8s.workload.kindcontainer.namedt.entity.container_groupprocess.technologywinlog.eventidwinlog.providerwinlog.taskwinlog.opcodewinlog.usernamewinlog.keywordsoperatorMATCHESvalues