> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Triage Sentry issues and releases from Guild agents

> Connect Guild agents to the Sentry REST API with an auth token to read issues, events, and releases, and limit write and delete tools with credential policies.

Integrations · Sentry

Guild agents list and inspect Sentry issues, read the events and stack traces behind them, and check releases and monitors through the Sentry REST API. Guild stores your Sentry token and injects it server-side, so agent code never sees it. Credential policies decide which Sentry operations each agent may call.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Sentry.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Sentry to your first agent.

## What the Sentry integration exposes

The integration is `guildai~sentry`. Tools cover issues and their events, projects, releases, organizations, teams, members, cron monitors, replays, environments, dashboards, Discover queries, and integrations. Requests go to `https://sentry.io`.

The set isn't read-only. It includes tools that update issues, change project settings, and permanently remove issues, such as `sentry_bulk_remove_a_list_of_issues`.

## How it works

**1. Create a Sentry token**

In Sentry, open **User settings > Personal tokens** and create a token with the scopes your agent needs, such as `event:read`, `project:read`, and `org:read` for triage.

**2. Connect the token in Guild**

Go to **Access & setup > Credentials**, click **Connect**, select **sentry**, and paste the token into **API Key**.

**3. Import the tools you need**

Import `SentryTools` from `@guildai-services/guildai~sentry` and use `pick()` to give the agent only the tools its job needs.

## Why Sentry access needs governing

The same integration that reads a stack trace can delete a project. Two controls narrow it. Grant the Sentry token only the scopes the agent needs, and write [credential policies](https://docs.guild.ai/platform/credential-policies.md) that Guild checks before any request reaches Sentry. A triage agent can read issues and events while a DENY rule blocks every `delete` and `remove` tool.

## Authentication

* **Type:** API key
* **Header:** Guild sends the token as `Authorization: Bearer <token>`
* **Token:** a Sentry personal token, limited to the scopes you grant

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { SentryTools } from "@guildai-services/guildai~sentry"
import { llmAgent, pick } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You summarize new Sentry issues and their likely cause.",
  tools: {
    ...pick(SentryTools, [
      "sentry_list_organization_issues",
      "sentry_list_organization_issue_events",
      "sentry_list_organization_releases",
    ]),
  },
})
```

Tools are named with the `sentry_` prefix. The integration has more than 200 tools, so pick the ones the agent needs rather than spreading the whole set.

## Tools

Tools in the latest published version of `guildai~sentry`:

> [accordion] All 219 tools
>
> | Tool | What it does |
> | - | - |
> | `sentry_add_organization_member` | Add or invite a member to an organization. |
> | `sentry_add_organization_member_team` | This request can return various success codes depending on the context of the team: - `201`: The member has been successfully added. - `202`: The member needs permission to join the team and an… |
> | `sentry_add_project_symbol_source` | Add a custom symbol source to a project. |
> | `sentry_add_project_team` | Give a team access to a project. |
> | `sentry_bulk_mutate_a_list_of_issues` | Bulk mutate various attributes on issues. |
> | `sentry_bulk_remove_a_list_of_issues` | Permanently remove the given issues. |
> | `sentry_bulk_update_project_environments` | Bulk update the visibility for a project's environments. |
> | `sentry_create_an_external_issue_and_link_it_to_an_issue` | Create a new issue in the external provider (such as a Jira ticket or GitHub issue) and link it to the given Sentry issue. |
> | `sentry_create_organization_dashboard` | Create a new dashboard for the given Organization |
> | `sentry_create_organization_discover_saved_query` | Create a new saved query for the given organization. |
> | `sentry_create_organization_external_user` | Link a user from an external provider to a Sentry user. |
> | `sentry_create_organization_forwarding` | Creates a new data forwarder for an organization. |
> | `sentry_create_organization_monitor` | Create a new monitor. |
> | `sentry_create_organization_notifications_action` | Creates a new Notification Action for Spike Protection. |
> | `sentry_create_organization_project` | Create a new project for an organization. |
> | `sentry_create_organization_project_detector` | Create a Monitor for a project |
> | `sentry_create_organization_release` | Create a new release for the given organization. |
> | `sentry_create_organization_release_deploy` | Create a deploy for a given release. |
> | `sentry_create_organization_team` | Create a new team bound to an organization. |
> | `sentry_create_organization_workflow` | Creates an alert for an organization |
> | `sentry_create_or_update_an_external_issue` | Create or update an external issue from an integration platform integration. |
> | `sentry_create_project_key` | Create a new client key bound to a project. |
> | `sentry_create_project_replay_deletion_job` | Create a new replay deletion job. |
> | `sentry_create_team_external_team` | Link a team from an external provider to a Sentry team. |
> | `sentry_create_team_project` | Create a new project bound to a team. |
> | `sentry_delete_an_external_issue` | Delete an external issue. |
> | `sentry_delete_organization_dashboard` | Delete an organization's custom dashboard. |
> | `sentry_delete_organization_detector` | Delete a monitor |
> | `sentry_delete_organization_detectors` | Bulk delete Monitors for a given organization |
> | `sentry_delete_organization_discover_saved_query` | Delete a saved query. |
> | `sentry_delete_organization_external_user` | Delete the link between a user from an external provider and a Sentry user. |
> | `sentry_delete_organization_forwarding` | Deletes a data forwarder for an organization. |
> | `sentry_delete_organization_integration` | OrganizationIntegrationBaseEndpoints expect both Integration and. |
> | `sentry_delete_organization_issue` | Asynchronously queue an individual issue for deletion. |
> | `sentry_delete_organization_issues` | Permanently remove the given issues. |
> | `sentry_delete_organization_member` | Remove an organization member. |
> | `sentry_delete_organization_member_team` | Delete an organization member from a team. |
> | `sentry_delete_organization_monitor` | Delete a monitor or monitor environments. |
> | `sentry_delete_organization_notifications_action` | Deletes a Spike Protection Notification Action. |
> | `sentry_delete_organization_preprod_artifact_snapshot` | Delete a snapshot and all associated data (images, comparisons, metrics). |
> | `sentry_delete_organization_release` | Permanently remove a release and all of its files. |
> | `sentry_delete_organization_release_file` | Permanently remove a file from a release. |
> | `sentry_delete_organization_scim_v2_group` | Delete a team with a SCIM Group DELETE Request. |
> | `sentry_delete_organization_scim_v2_user` | Delete an organization member with a SCIM User DELETE Request. |
> | `sentry_delete_organization_workflow` | Deletes an alert. |
> | `sentry_delete_organization_workflows` | Bulk delete alerts for a given organization |
> | `sentry_delete_project` | Schedules a project for deletion. |
> | `sentry_delete_project_key` | Delete a client key for a given project. |
> | `sentry_delete_project_monitor` | Delete a monitor or monitor environments. |
> | `sentry_delete_project_release_file` | Permanently remove a file from a release. |
> | `sentry_delete_project_replay` | Delete a replay. |
> | `sentry_delete_project_symbol_source` | Delete a custom symbol source from a project. |
> | `sentry_delete_project_team` | Revoke a team's access to a project. |
> | `sentry_delete_sentry_app` | Delete a custom integration. |
> | `sentry_delete_team` | Schedules a team for deletion. |
> | `sentry_delete_team_external_team` | Delete the link between a team from an external provider and a Sentry team. |
> | `sentry_disable_spike_protection` | Disables Spike Protection feature for some of the projects within the organization. |
> | `sentry_enable_spike_protection` | Enables Spike Protection feature for some of the projects within the organization. |
> | `sentry_get_organization` | Return details on an individual organization, including various details such as membership access and teams. |
> | `sentry_get_organization_config_integrations` | Get integration provider information about all available integrations for an organization. |
> | `sentry_get_organization_dashboard` | Return details about an organization's custom dashboard. |
> | `sentry_get_organization_detector` | Return details on an individual monitor |
> | `sentry_get_organization_discover_saved_query` | Retrieve a saved query. |
> | `sentry_get_organization_integration` | OrganizationIntegrationBaseEndpoints expect both Integration and. |
> | `sentry_get_organization_issue` | Return details on an individual issue, including its basic stats, comment and user-report counts, and a summary of the latest event. |
> | `sentry_get_organization_issue_autofix_state` | Retrieve the current detailed state of an issue fix process for a specific issue including. |
> | `sentry_get_organization_issue_event` | Retrieves the details of an issue event. |
> | `sentry_get_organization_issue_tag` | Return a list of values associated with this key for an issue. |
> | `sentry_get_organization_member` | Retrieve an organization member's details. |
> | `sentry_get_organization_monitor` | Retrieves details for a monitor. |
> | `sentry_get_organization_notifications_action` | Returns a serialized Spike Protection Notification Action object. |
> | `sentry_get_organization_preprod_artifact_install_details` | Retrieve install info for a given artifact. |
> | `sentry_get_organization_preprod_artifact_size_analysis` | Retrieve size analysis results for a given artifact. |
> | `sentry_get_organization_preprod_artifact_snapshot` | Retrieve full details for a snapshot, including categorized image lists and comparison status. |
> | `sentry_get_organization_preprod_artifact_snapshot_image` | Retrieve detailed information for a single image within a snapshot. |
> | `sentry_get_organization_preprod_artifact_snapshot_latest_base` | Retrieve the most recent base snapshot for a given app. |
> | `sentry_get_organization_profiling_flamegraph` | Retrieve an aggregated flamegraph for the organization, built from the requested data source (transactions, profiles, functions, or spans). |
> | `sentry_get_organization_release` | Return details on an individual release. |
> | `sentry_get_organization_release_file` | Return metadata for an individual file within a release. |
> | `sentry_get_organization_replay` | Return details on an individual replay. |
> | `sentry_get_organization_replay_count` | Return a count of replays for a list of issue or transaction IDs. |
> | `sentry_get_organization_scim_v2_group` | Query an individual team with a SCIM Group GET Request. - Note that the members field will only contain up to 10000 members. |
> | `sentry_get_organization_scim_v2_user` | Query an individual organization member with a SCIM User GET Request. - The `name` object will contain fields `firstName` and `lastName` with the values of `N/A`. |
> | `sentry_get_organization_sessions` | Returns a time series of release health session statistics for projects bound to an organization. |
> | `sentry_get_organization_stats_summary` | Query summarized event counts by project for your Organization. |
> | `sentry_get_organization_trace` | Retrieve the spans, errors, and (optionally) uptime checks that make up a single trace. |
> | `sentry_get_organization_trace_meta` | Retrieve aggregate metadata for a single trace, including counts of spans, errors, performance issues, logs, and metrics, along with per-span-operation and per-transaction child-count breakdowns. |
> | `sentry_get_organization_workflow` | Returns an alert. |
> | `sentry_get_project` | Return details on an individual project. |
> | `sentry_get_project_environment` | Return details on a project environment. |
> | `sentry_get_project_event` | Return details on an individual event. |
> | `sentry_get_project_event_attachment` | Retrieve metadata for a single attachment on an event, or download its contents by passing the `download` query parameter. |
> | `sentry_get_project_event_source_map_debug` | Return a list of source map errors for a given event. |
> | `sentry_get_project_installable_build_latest` | Get the latest installable build for a project. |
> | `sentry_get_project_key` | Return a client key bound to a project. |
> | `sentry_get_project_monitor` | Retrieves details for a monitor. |
> | `sentry_get_project_ownership` | Returns details on a project's ownership configuration. |
> | `sentry_get_project_preprod_size_analysis_status_check_rules` | Retrieve the current Size Analysis status check rules configured for a project. |
> | `sentry_get_project_preprod_snapshot_status_check_rules` | Retrieve the current Snapshot status check rules configured for a project. |
> | `sentry_get_project_profiling_profile` | Retrieve a single profile by its ID. |
> | `sentry_get_project_release_file` | Return metadata for an individual file within a release. |
> | `sentry_get_project_replay_deletion_job` | Fetch a replay delete job instance. |
> | `sentry_get_project_replay_recording_segment` | Return a replay recording segment. |
> | `sentry_get_sentry_app` | Retrieve a custom integration. |
> | `sentry_get_team` | Return details on an individual team. |
> | `sentry_link_an_existing_external_issue_to_an_issue` | Link an issue that already exists in the external provider (such as a Jira ticket or GitHub issue) to the given Sentry issue. |
> | `sentry_link_project_repository` | Link a repository to a project. |
> | `sentry_list_an_organizations_integration_platform_installations` | Return a list of integration platform installations for a given organization. |
> | `sentry_list_a_projects_issues` | List a project's issues. Deprecated; use sentry\_list\_organization\_issues. |
> | `sentry_list_a_projects_service_hooks` | Return a list of service hooks bound to a project. |
> | `sentry_list_a_projects_user_feedback` | Return a list of user feedback items within this project. |
> | `sentry_list_a_tags_values` | Return a list of values associated with this key. |
> | `sentry_list_organization_dashboards` | Retrieve a list of custom dashboards that are associated with the given organization. |
> | `sentry_list_organization_detectors` | List an Organization's Monitors |
> | `sentry_list_organization_discover_saved_queries` | Retrieve a list of saved queries that are associated with the given organization. |
> | `sentry_list_organization_environments` | Lists an organization's environments. |
> | `sentry_list_organization_events` | Retrieves explore data for a given organization. |
> | `sentry_list_organization_events_timeseries` | Retrieves explore data for a given organization as a timeseries. |
> | `sentry_list_organization_forwarding` | Returns a list of data forwarders for an organization. |
> | `sentry_list_organization_integrations` | Lists all the available Integrations for an Organization. |
> | `sentry_list_organization_issue_events` | Return a list of error events bound to an issue |
> | `sentry_list_organization_issue_external_issues` | Retrieve custom integration issue links for the given Sentry issue |
> | `sentry_list_organization_issue_hashes` | List the hashes that make up an issue. |
> | `sentry_list_organization_issues` | Return a list of issues for an organization. |
> | `sentry_list_organization_issue_tag_values` | Returns a list of values associated with this key for an issue. |
> | `sentry_list_organization_members` | List all organization members. |
> | `sentry_list_organization_monitor_checkins` | Retrieve a list of check-ins for a monitor |
> | `sentry_list_organization_monitors` | Lists monitors, including nested monitor environments. |
> | `sentry_list_organization_notifications_actions` | Returns all Spike Protection Notification Actions for an organization. |
> | `sentry_list_organization_profiling_chunks` | Retrieve continuous profiling data for a profiler over a time range. |
> | `sentry_list_organization_project_keys` | Return a list of client keys (DSNs) for all projects in an organization. |
> | `sentry_list_organization_projects` | Return a list of projects bound to a organization. |
> | `sentry_list_organization_relay_usage` | Return a list of trusted relays bound to an organization. |
> | `sentry_list_organization_release_commits` | Retrieve a list of commits for a given release. |
> | `sentry_list_organization_release_deploys` | Returns a list of deploys based on the organization, version, and project. |
> | `sentry_list_organization_release_files` | Retrieve a list of files for a given release. |
> | `sentry_list_organization_releases` | Return a list of releases for a given organization, sorted by most recent. |
> | `sentry_list_organization_release_threshold_statuses` | `[WARNING]`: This API is an experimental Alpha feature and is subject to change! |
> | `sentry_list_organization_replays` | Return a list of replays belonging to an organization. |
> | `sentry_list_organization_replay_selectors` | Return a list of selectors for a given organization. |
> | `sentry_list_organization_repo_commits` | List a Repository's Commits |
> | `sentry_list_organization_repos` | Return a list of version control repositories for a given organization. |
> | `sentry_list_organizations` | Return a list of organizations available to the authenticated session in a region. |
> | `sentry_list_organization_scim_v2_groups` | Returns a paginated list of teams bound to a organization with a SCIM Groups GET Request. |
> | `sentry_list_organization_scim_v2_users` | Returns a paginated list of members bound to a organization with a SCIM Users GET Request. |
> | `sentry_list_organization_sentry_apps` | Retrieve the custom integrations for an organization |
> | `sentry_list_organization_stats_v2` | Query event counts for your Organization. |
> | `sentry_list_organization_tags` | Return a list of tag keys for the given organization. |
> | `sentry_list_organization_teams` | Returns a list of teams bound to a organization. |
> | `sentry_list_organization_trace_item_attributes` | List the attribute keys available on a given trace item dataset (spans, logs, trace metrics, etc.), with optional substring and structured filtering. |
> | `sentry_list_organization_user_teams` | Returns a list of teams the user has access to in the specified organization. |
> | `sentry_list_organization_workflows` | Returns a list of alerts for a given organization |
> | `sentry_list_project_debug_files` | Retrieve a list of debug information files for a given project. |
> | `sentry_list_project_environments` | Lists a project's environments. |
> | `sentry_list_project_event_attachments` | Retrieve a list of attachments uploaded for a given event. |
> | `sentry_list_project_events` | Return a list of events bound to a project. |
> | `sentry_list_project_filters` | Retrieve a list of filters for a given project. `active` will be either a boolean or a list for the legacy browser filters. |
> | `sentry_list_project_keys` | Return a list of client keys bound to a project. |
> | `sentry_list_project_members` | Returns a list of active organization members that belong to any team assigned to the project. |
> | `sentry_list_project_monitor_checkins` | Retrieve a list of check-ins for a monitor |
> | `sentry_list_project_release_commits` | Retrieve a list of commits for a given release. |
> | `sentry_list_project_release_files` | Retrieve a list of files for a given release. |
> | `sentry_list_project_releases` | Retrieve a list of releases for a given project. |
> | `sentry_list_project_replay_clicks` | Retrieve a collection of RRWeb DOM node-ids and the timestamp they were clicked. |
> | `sentry_list_project_replay_deletion_jobs` | Retrieve a collection of replay delete jobs. |
> | `sentry_list_project_replay_recording_segments` | Return a collection of replay recording segments. |
> | `sentry_list_project_replay_viewed_by` | Return a list of users who have viewed a replay. |
> | `sentry_list_project_stats` | Return a set of points representing a normalized timestamp and the number of events seen in the period. |
> | `sentry_list_project_symbol_sources` | List custom symbol sources configured for a project. |
> | `sentry_list_project_teams` | Return a list of teams that have access to this project. |
> | `sentry_list_project_users` | Return a list of users seen within this project. |
> | `sentry_list_seer_models` | Get list of actively used LLM model names from Seer. |
> | `sentry_list_team_members` | List all members on a team. |
> | `sentry_list_team_projects` | Return a list of projects bound to a team. |
> | `sentry_provision_organization_scim_v2_group` | Create a new team bound to an organization via a SCIM Groups POST. |
> | `sentry_provision_organization_scim_v2_user` | Create a new Organization Member via a SCIM Users POST Request. |
> | `sentry_register_a_new_service_hook` | Register a new service hook on a project. |
> | `sentry_remove_a_service_hook` | Remove a service hook. |
> | `sentry_resolve_organization_event_id` | This resolves an event ID to the project slug and internal issue ID and internal event ID. |
> | `sentry_resolve_organization_short_id` | Resolve a short ID to the project slug and group details. |
> | `sentry_retrieve_an_integrations_issue_config_for_an_issue` | Retrieve the form fields needed to either link an existing external issue (such as a Jira ticket or GitHub issue) to a Sentry issue, or create a new one. |
> | `sentry_retrieve_a_service_hook` | Return a service hook bound to a project. |
> | `sentry_retrieve_files_changed_in_a_releases_commits` | Retrieve files changed in a release's commits |
> | `sentry_retrieve_trace_item_statistics` | Compute statistics, such as attribute value distributions, over the trace items (spans or occurrences) matching the given query within the requested time range. |
> | `sentry_start_organization_issue_autofix` | Trigger a Seer Issue Fix run for a specific issue. |
> | `sentry_submit_user_feedback` | \*This endpoint is DEPRECATED. |
> | `sentry_unlink_an_external_issue_from_an_issue` | Remove the link between a Sentry issue and an external issue. |
> | `sentry_update_a_service_hook` | Update a service hook. |
> | `sentry_update_organization` | Update various attributes and configurable settings for the given organization. |
> | `sentry_update_organization_dashboard` | Edit an organization's custom dashboard as well as any bulk edits on widgets that may have been made. (For example, widgets that have been rearranged, updated queries and fields, specific display… |
> | `sentry_update_organization_detector` | Update an existing monitor |
> | `sentry_update_organization_detectors` | Bulk enable or disable an Organization's Monitors |
> | `sentry_update_organization_discover_saved_query` | Modify a saved query. |
> | `sentry_update_organization_external_user` | Update a user in an external provider that is currently linked to a Sentry user. |
> | `sentry_update_organization_forwarding` | Updates a data forwarder for an organization or update a project-specific override. |
> | `sentry_update_organization_issue` | Update an individual issue's attributes. |
> | `sentry_update_organization_issues` | Bulk mutate various attributes on a maxmimum of 1000 issues. - For non-status updates, the `id` query parameter is required. - For status updates, the `id` query parameter may be omitted to update… |
> | `sentry_update_organization_member` | Update a member's organization-level and team-level roles. |
> | `sentry_update_organization_member_team` | The relevant organization member must already be a part of the team. |
> | `sentry_update_organization_monitor` | Update a monitor. |
> | `sentry_update_organization_notifications_action` | Updates a Spike Protection Notification Action. |
> | `sentry_update_organization_release` | Update a release. |
> | `sentry_update_organization_release_file` | Update metadata of an existing release file. |
> | `sentry_update_organization_scim_v2_group` | Update a team's attributes with a SCIM Group PATCH Request. |
> | `sentry_update_organization_scim_v2_user` | Update an organization member's attributes with a SCIM PATCH Request. |
> | `sentry_update_organization_workflow` | Updates an alert. |
> | `sentry_update_organization_workflows` | Bulk enable or disable alerts for a given Organization |
> | `sentry_update_project` | Update various attributes and configurable settings for the given project. |
> | `sentry_update_project_environment` | Update the visibility for a project environment. |
> | `sentry_update_project_filter` | Update various inbound data filters for a project. |
> | `sentry_update_project_key` | Update various settings for a client key. |
> | `sentry_update_project_monitor` | Update a monitor. |
> | `sentry_update_project_ownership` | Updates ownership configurations for a project. |
> | `sentry_update_project_release_file` | Update metadata of an existing release file. |
> | `sentry_update_project_symbol_source` | Update a custom symbol source in a project. |
> | `sentry_update_sentry_app` | Update an existing custom integration. |
> | `sentry_update_team` | Update various attributes and configurable settings for the given team. |
> | `sentry_update_team_external_team` | Update a team in an external provider that is currently linked to a Sentry team. |
> | `sentry_upload_project_preprod_artifact_snapshot` | Upload a new snapshot with image metadata. |

## Frequently asked questions

> [accordion] Does the Sentry integration work with self-hosted Sentry?
>
> No. Requests go to `https://sentry.io`, and the address is fixed when the integration is published. For a self-hosted instance, [create a custom integration](https://docs.guild.ai/services/create-an-integration.md) with your own base URL.

> [accordion] Can a new Sentry issue trigger a Guild agent?
>
> Not yet. Guild doesn't receive Sentry alerts, so you can't create an event trigger for Sentry. Run the agent on a [schedule](https://docs.guild.ai/platform/schedule-triggers.md) instead.

> [accordion] Can I keep an agent from deleting Sentry data?
>
> Yes, in two layers. Leave admin and write scopes off the token, and write a credential policy that denies delete and remove operations. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md).

## Related

**Also runs on Guild:** [Datadog](https://docs.guild.ai/integrations/datadog.md) · [New Relic](https://docs.guild.ai/integrations/newrelic.md) · [Splunk](https://docs.guild.ai/integrations/splunk.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)