• Home
  • Dynatrace API
  • Environment
  • Audit logs
  • GET audit log

Audit logs API - GET audit log

Fetches the audit log of your Dynatrace environment.

The full list can be lengthy, so you can narrow it down by specifying filter parameters, like tags. See the Parameters section for more details.

You can limit the output by using the pagination:

  1. Specify the number of results per page in the pageSize query parameter.
  2. Then use the cursor from the nextPageKey field of the previous response in the nextPageKey query parameter to obtain subsequent pages.
GETManagedDynatrace for Governmenthttps://{your-domain}/e/{your-environment-id}/api/v2/auditlogs
SaaShttps://{your-environment-id}.live.dynatrace.com/api/v2/auditlogs
Environment ActiveGatehttps://{your-activegate-domain}/e/{your-environment-id}/api/v2/auditlogs

Authentication

To execute this request, you need an access token with auditLogs.read scope.

To learn how to obtain and use it, see Tokens and authentication.

Parameters

ParameterTypeDescriptionInRequired
nextPageKeystring

The cursor for the next page of results. You can find it in the nextPageKey field of the previous response.

The first page is always returned if you don't specify the nextPageKey query parameter.

When the nextPageKey is set to obtain subsequent pages, you must omit all other query parameters.

queryoptional
pageSizeinteger

The amount of log entries in a single response payload.

The maximal allowed page size is 5000.

If not set, 1000 is used.

queryoptional
filterstring

Filters the audit log. You can use the following criteria:

  • User: user("userIdentification"). The EQUALS operator applies.
  • Event type: eventType("value"). The EQUALS operator applies.
  • Category of a logged operation: category("value"). The EQUALS operator applies.
  • Entity ID: entityId("id"). The CONTAINS operator applies.

For each criterion, you can specify multiple alternatives with comma-separated values. In this case, the OR logic applies. For example, eventType("CREATE","UPDATE") means eventType can be "CREATE" or "UPDATE".

You can specify multiple comma-separated criteria, such as eventType("CREATE","UPDATE"),category("CONFIG"). Only results matching all criteria are included in response.

Specify the value of a criterion as a quoted string. The following special characters must be escaped with a tilde (~) inside quotes:

  • Tilde ~
  • Quote "
queryoptional
fromstring

The start of the requested timeframe.

You can use one of the following formats:

  • Timestamp in UTC milliseconds.
  • Human-readable format of 2021-01-25T05:57:01.123+01:00. If no time zone is specified, UTC is used. You can use a space character instead of the T. Seconds and fractions of a second are optional.
  • Relative timeframe, back from now. The format is now-NU/A, where N is the amount of time, U is the unit of time, and A is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, now-1y/w is one year back, aligned by a week. You can also specify relative timeframe without an alignment: now-NU. Supported time units for the relative timeframe are:
    • m: minutes
    • h: hours
    • d: days
    • w: weeks
    • M: months
    • y: years

If not set, the relative timeframe of two weeks is used (now-2w).

queryoptional
tostring

The end of the requested timeframe.

You can use one of the following formats:

  • Timestamp in UTC milliseconds.
  • Human-readable format of 2021-01-25T05:57:01.123+01:00. If no time zone is specified, UTC is used. You can use a space character instead of the T. Seconds and fractions of a second are optional.
  • Relative timeframe, back from now. The format is now-NU/A, where N is the amount of time, U is the unit of time, and A is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, now-1y/w is one year back, aligned by a week. You can also specify relative timeframe without an alignment: now-NU. Supported time units for the relative timeframe are:
    • m: minutes
    • h: hours
    • d: days
    • w: weeks
    • M: months
    • y: years

If not set, the current timestamp is used.

queryoptional
sortstring

The sorting of audit log entries:

  • timestamp: Oldest first.
  • -timestamp: Newest first.

If not set, the newest first sorting is applied.

queryoptional

Response

Response codes

CodeTypeDescription
200AuditLog

Success

Response body objects

The AuditLog object

The audit log of your environment.

ElementTypeDescription
totalCountinteger

The total number of entries in the result.

pageSizeinteger

The number of entries per page.

nextPageKeystring

The cursor for the next page of results. Has the value of null on the last page.

Use it in the nextPageKey query parameter to obtain subsequent pages of the result.

auditLogsAuditLogEntry[]

A list of audit log entries ordered by the creation timestamp.

The AuditLogEntry object

An entry of the audit log.

ElementTypeDescription
logIdstring

The ID of the log entry.

eventTypestring

The type of the recorded operation.

The element can hold these values
  • CREATE
  • DELETE
  • GENERAL
  • GET
  • LOGIN
  • LOGOUT
  • PATCH
  • POST
  • PUT
  • READ
  • REMOTE_CONFIGURATION_MANAGEMENT
  • REVOKE
  • TAG_ADD
  • TAG_REMOVE
  • TAG_UPDATE
  • UPDATE
categorystring

The category of the recorded operation.

The element can hold these values
  • ACTIVE_GATE
  • AGENT
  • CONFIG
  • DEBUG_UI
  • MANUAL_TAGGING_SERVICE
  • TOKEN
  • WEB_UI
entityIdstring

The ID of an entity from the category.

For example, it can be config ID for the CONFIG category or token ID for the TOKEN category.

environmentIdstring

The ID of the Dynatrace environment where the recorded operation occurred.

userstring

The ID of the user who performed the recorded operation.

userTypestring

The type of the authentication of the user.

The element can hold these values
  • PUBLIC_TOKEN_IDENTIFIER
  • REQUEST_ID
  • SERVICE_NAME
  • TOKEN_HASH
  • USER_NAME
userOriginstring

The origin and the IP address of the user.

timestampinteger

The timestamp of the record creation, in UTC milliseconds.

successboolean

The recorded operation is successful (true) or failed (false).

messagestring

The logged message.

patchobject

The patch of the recorded operation as the JSON representation.

The format is an enhanced RFC 6902. The patch also carries the previous value in the oldValue field.

Response body JSON model

json
{ "totalCount": 10, "pageSize": 5, "nextPageKey": "___a7acX3q0AAAAAACJidWlsdGluOnNlcnZpY2lUVEJCUzBaNVIxVjJOSGt6Y3oyLTcwMUZWRkxlclH__9rtpxferQ", "auditLogs": [ { "logId": "197425568800060000", "eventType": "UPDATE", "category": "CONFIG", "entityId": "MOBILE_RUM: MOBILE_APPLICATION-752C223D59734CD2", "environmentId": "prod-env-13", "user": "test.user@company.com", "userType": "USER_NAME", "userOrigin": "webui (192.168.0.2)", "timestamp": 1974255688445, "success": true, "patch": [ { "op": "replace", "path": "/refreshTimeIntervalMillis", "value": 30000, "oldValue": 20000 } ] } ] }

Example

In this example, the request fetches all logins (filter=eventType(LOGIN)) from the audit log of the mySampleEnv environment for the last week (from=now-1w).

The API token is passed in the Authorization header.

The response is truncated to the first three entries.

Curl

bash
curl -X GET \ 'https://mySampleEnv.live.dynatrace.com/api/v2/auditlogs?filter=eventType%28LOGIN%29&from=now-1w' \ -H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890'

Request URL

plaintext
https://mySampleEnv.live.dynatrace.com/api/v2/auditlogs?filter=eventType%28LOGIN%29&from=now-1w

Response body

json
{ "totalCount": 5820, "nextPageKey": "vu8y3hPZ3q0AAAAAAi_neQJ8qUAAAAFu0T-ECgAAAW71TAgKAAAD6AAQZXZlbnRUeXBlKExPR0lOKQC-7zLeE9nerQ", "auditLogs": [ { "logId": "157607341600050000", "eventType": "LOGIN", "category": "WEB_UI", "entityId": "240.204.62.255", "environmentId": "yasmuoujsw", "user": "Dynatrace support user #877988415", "userType": "USER_NAME", "userOrigin": "Forwarded: 240.204.62.255", "timestamp": 1576073415531, "success": true }, { "logId": "157607338800050000", "eventType": "LOGIN", "category": "WEB_UI", "entityId": "55.199.177.119", "environmentId": "yasmuoujsw", "user": "Dynatrace support user #490812376", "userType": "USER_NAME", "userOrigin": "Forwarded: 55.199.177.119", "timestamp": 1576073388150, "success": true }, { "logId": "157607338300060000", "eventType": "LOGIN", "category": "WEB_UI", "entityId": "75.16.11.184", "environmentId": "umsaywsjuo", "user": "Dynatrace support user #765684830", "userType": "USER_NAME", "userOrigin": "Forwarded: 75.16.11.184", "timestamp": 1576073381543, "success": true } ] }

Response code

200

Related topics
  • Manage audit logs

    Learn why audit logs are important for the data privacy and security of your application.