Migrate from Log Monitoring API v1 to Log Classic API

Log Monitoring API v1 has been deprecated with Dynatrace version 1.284. Its replacement is Log Monitoring API. We recommend that you migrate to the new API at your earliest convenience.

The migration affects endpoint URLs, query parameters, and response/request body parameters, as well as the scope of the token for request authentication.

New features

Log Classic API offers you the following new features:

  • You can search or export log data that match provided criteria in the global log storage (with up to 35 days of retention).
  • The new version gets the aggregated log records that match the provided criteria.
  • You can ingest log data using REST API.

Licensing

The ingestion of custom events consumes Davis Data Units (DDUs) from the logs pool.

Base URL

Log Classic API new

  • /api/v2/logs/aggregate
  • /api/v2/logs/export
  • /api/v2/logs/ingest
  • /api/v2/logs/search

Log Monitoring v1 old

  • /api/v1/entity/infrastructure/custom-devices
  • /api/v1/entity/infrastructure/hosts
  • /api/v1/entity/infrastructure/process-groups

Authentication token scope

Read logs (logs.read)
Ingest logs (logs.ingest)
List, get, analyse logs of custom devices, hosts or process groups (LogExport)

Parameters

To learn about new query/body parameters, see the documentation of individual requests in Log Classic API.

Examples

Here are some examples of differences in API usage.

Retrieve host OS system log file names

Find process group file log records for a given query

Find number of occurrences of some fields of a process group file log records