Data Pipeline
Series of processes that move and transform data between systems for analysis, storage, or further processing.
Overview
Database Table
Contention on Database Table Locks
The database table is experiencing an abnormally high rate of exclusive locks, preventing multiple transactions from accessing the table simultaneously. This creates a bottleneck that significantly degrades performance for all client applications depending on this table. Excessive locking typically occurs due to long-running transactions, lock contention between multiple transactions, inefficient transaction design, inappropriate isolation levels, or missing indexes leading to table scans instead of index seeks.
Schema Change Causing Table Lock Contention
The database table is experiencing an unusually high rate of Data Dictionary Lock (DDL), which blocks both read and write operations during schema modifications. This significantly impacts all client applications, causing service disruptions and performance degradation.
Table Access Failure in Database
The database table is experiencing performance degradation or errors, causing disruptions for client applications. This results in slow query response times, potential errors, and degraded service performance for systems that depend on this table.
HTTP Path
Authentication Rejection in HTTP Path
The HTTP path is rejecting requests as unauthenticated or forbidden across its callers. The problem is most likely in this endpoint's authentication or authorization setup, such as a new or tightened authorization policy, a changed token audience or required scope, or a route-specific auth middleware, rather than in any single client.
Faulty Error Handling in HTTP Path
The HTTP path is experiencing a high rate of errors, causing disruptions for clients. This can lead to degraded performance, failed requests, or complete service unavailability, significantly affecting the user experience.
Policy Rejection in HTTP Path
The HTTP path is rejecting requests with HTTP 451 "Unavailable For Legal Reasons" across its callers. A resource-gating, geo-blocking, legal-hold, or feature-flag rule that covers this endpoint, for example a path prefix that matches more routes than intended, is the likely cause.
Slow Execution in HTTP Path Handler
The HTTP path is experiencing congestion, resulting in high latency for clients. This suggests that the system is unable to handle the current load efficiently, causing delays in response times. Congestion often occurs when the service receives more requests than it can handle within its capacity.
Throttling Rejection in HTTP Path
The HTTP path is throttling requests with HTTP 429 "Too Many Requests" across its callers. The problem is most likely in this endpoint's rate limit or quota rather than in any single client's request rate.
MCP Tool
Authentication Rejection in MCP Tool
The MCP tool is rejecting calls as unauthenticated or forbidden across its callers. The problem is most likely in this tool's authentication or authorization setup, such as a new or tightened authorization policy, a changed token audience or required scope, or tool-specific auth middleware on the MCP server, rather than in any single client.
Faulty Error Handling in MCP Tool
The MCP tool is returning a high rate of errors, causing failed tool calls for the clients and agents that invoke it. Typical causes are tool execution failures, arguments that do not match the tool schema, failing downstream dependencies, or expired credentials and misconfigured tool settings on the MCP server.
Policy Rejection in MCP Tool
The MCP tool is rejecting calls because of a policy across its callers. A resource-gating, geo-blocking, legal-hold, or feature-flag rule that covers this tool, for example a tool name or namespace match that is broader than intended, is the likely cause.
Slow Execution in MCP Tool
The MCP tool is experiencing congestion, resulting in high latency for the clients and agents that invoke it. This suggests that the tool or its MCP server cannot handle the current invocation load, for example because of resource constraints on the MCP server, slow downstream operations, expensive tool logic, or a surge in tool calls.
Throttling Rejection in MCP Tool
The MCP tool is throttling calls across its callers. The problem is most likely in this tool's rate limit or quota rather than in any single client's call rate.
RPC Method
Authentication Rejection in RPC Method
The RPC method is rejecting requests as unauthenticated or forbidden across its callers. The problem is most likely in this endpoint's authentication or authorization setup, such as a new or tightened authorization policy, a changed token audience or required scope, or a route-specific auth middleware, rather than in any single client.
Faulty Error Handling in RPC Method
The RPC Method is experiencing a high rate of errors, causing disruptions for clients. This can lead to degraded performance, failed requests, or complete service unavailability, significantly affecting the user experience.
Slow Execution in RPC Method Handler
The RPC method is experiencing congestion, resulting in high latency for clients. This suggests that the system is unable to handle the current load efficiently, causing delays in response times. Congestion often occurs when the service receives more requests than it can handle within its capacity.
Throttling Rejection in RPC Method
The RPC method is throttling requests across its callers. The problem is most likely in this endpoint's rate limit or quota rather than in any single client's request rate.