Upcoming changes to the Access log API EAP
- We've made the decision to move to a different storage solution; this change means that historical data before June 8 will be lost starting 2023-07-12. We also anticipate that this new implementation of our storage solution will enhance the performance and reliability of our API by avoiding the throttling exceptions typically caused by our current solution. It also offers the added capability of supporting a combination of 'user' and 'path' filters.
- Each log item will now include an additional field “id”. This is used only for internal Zendesk purposes.
- Representation of GraphQL data
- The variables attribute will change from an object to a string
- GraphQL data that is longer than 255 characters will be truncated and represented by [...]
Example of truncated data
"timestamp": "2023-04-12T23:44:06Z",
"user_id": 1100049638794,
"ip_address": "52.40.158.85",
"url": "/graphql",
"method": "POST",
"status": 200,
"graphql": {
"operation_name": "user",
"operation_type": "QUERY",
"query": "query user($id: ID!) { user(id: $id) { id UserFragment __typename } } on TextUserFieldValue { value field { id key title isActive position __typename } __typename } ... ", <--- TRUNCATED DATA
"variables": {
"id": "1100049638794"
"origin_service": "Zendesk"