Skip to main content

​
Overview

The list_log_entries tool retrieves all log entries across your PagerDuty account. Log entries are records of all events on your account, providing a comprehensive audit trail of actions taken by users, services, and integrations.
This is a read-only tool that does not modify any data in your PagerDuty account. If no time range is specified, defaults to the last 7 days.

​
Parameters

​
since
datetime
The start of the date range to search. Defaults to 7 days ago if not specified.Example: "2024-01-01T00:00:00Z"
​
until
datetime
The end of the date range to search. Defaults to now if not specified.Example: "2024-01-31T23:59:59Z"
​
limit
integer
default:"100"
Maximum number of results to return. Must be between 1 and 10000.Example: 50
​
offset
integer
default:"0"
The offset for pagination. Used to retrieve additional pages of results.Example: 100
​
is_overview
boolean
If true, returns only the most important changes to incidents. Useful for getting a high-level view without excessive detail.Example: true
​
include
array
Include additional related resources in the response. Available options:
  • incidents - Include incident details
  • services - Include service details
  • channels - Include channel information
  • teams - Include team information
Example: ["incidents", "services"]
​
team_ids
array
Filter log entries by team IDs. Only returns log entries associated with the specified teams.Example: ["TEAM123", "TEAM456"]
​
time_zone
string
Time zone for the results. Uses standard timezone names.Example: "America/New_York" or "UTC"
​
total
boolean
Set to true to include the total count of log entries in the response.Example: true

​
Response

Returns a list of log entry objects.
​
response
array
Array of log entry objects

​
Example Usage

"Show me all log entries from the last 24 hours"

​
Use Cases

  • Audit trail - Review all actions taken on your PagerDuty account
  • Incident investigation - Trace the sequence of events during an incident
  • Compliance reporting - Generate reports of who did what and when
  • Team activity - Monitor activity for specific teams
  • User behavior analysis - Understand how users interact with PagerDuty
  • Integration monitoring - Track actions performed by integrations

​
Response Example

{
  "response": [
    {
      "id": "LOGENTRY123",
      "type": "acknowledge_log_entry",
      "summary": "Acknowledged by John Doe",
      "created_at": "2024-01-15T14:30:00Z",
      "agent": {
        "id": "PUSER123",
        "type": "user_reference",
        "summary": "John Doe"
      },
      "channel": {
        "type": "web"
      },
      "incident": {
        "id": "Q1INCIDENT",
        "type": "incident_reference"
      }
    }
  ]
}

​
Important Notes

  • Log entries are read-only and cannot be modified or deleted
  • The default time range is 7 days to ensure reasonable response times
  • Use is_overview: true to reduce noise in high-traffic accounts
  • Log entries include polymorphic types based on the action performed

Build docs developers (and LLMs) love

Get started for freeTalk to us