Skip to main content

​
Overview

The get_log_entry tool retrieves detailed information about a specific log entry. Log entries provide a complete audit record of actions taken on incidents, services, and other resources.
This is a read-only tool that does not modify any data in your PagerDuty account.

​
Parameters

​
log_entry_id
string
required
The unique identifier of the log entry to retrieve.Example: "LOGENTRY123"

​
Response

Returns a detailed log entry object.
​
id
string
The unique identifier of the log entry
​
type
string
The type of log entry. Common types include:
  • trigger_log_entry - Incident was triggered
  • acknowledge_log_entry - Incident was acknowledged
  • resolve_log_entry - Incident was resolved
  • assign_log_entry - Incident was assigned
  • escalate_log_entry - Incident was escalated
  • notify_log_entry - Notification was sent
  • annotate_log_entry - Note was added
​
summary
string
A short, human-readable description of the log entry
​
self
string
The API URL at which this log entry is accessible
​
html_url
string
The URL at which this log entry is accessible in the PagerDuty web UI
​
created_at
datetime
The date and time when this log entry was created
​
agent
object
The agent (user, service, or integration) that performed the action
​
channel
object
The channel through which the action was performed
​
service
object
Reference to the service associated with this log entry
​
incident
object
Reference to the incident associated with this log entry
​
teams
array
References to teams associated with this log entry

​
Example Usage

"Show me the details of log entry LOGENTRY123"

​
Use Cases

  • Audit investigation - Review the complete details of a specific action
  • Incident timeline - Understand who did what and when during an incident
  • Compliance - Verify actions for compliance and security reviews
  • Troubleshooting - Understand the sequence of automated actions
  • User activity - Track specific user actions

​
Response Example

{
  "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",
    "html_url": "https://acme.pagerduty.com/users/PUSER123"
  },
  "channel": {
    "type": "web"
  },
  "service": {
    "id": "PSVC456",
    "type": "service_reference",
    "summary": "Production API"
  },
  "incident": {
    "id": "Q1INCIDENT",
    "type": "incident_reference",
    "summary": "[#123] Database connection timeout"
  }
}

​
Important Notes

  • Log entries are read-only and cannot be modified
  • Log entries use polymorphic types - the fields available depend on the log entry type
  • The agent field may reference users, services, or integrations depending on who/what performed the action
  • The channel field indicates how the action was performed (web, API, mobile, etc.)

Build docs developers (and LLMs) love

Get started for freeTalk to us