Monitor rate limiting through observability and audit fields
- Last Updated: December 23, 2025
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
The OpenEdge MCP Server records audit events for every request that is either allowed or denied by the rate limiting mechanism. These events help administrators monitor system behavior and troubleshoot issues.
The following table lists the fields included in each audit event:
| Field | Description |
|---|---|
ts |
Specifies the timestamp of the event in UTC format. |
category |
Specifies the category of the event. For rate limiting, this
value is rate_limit. |
action |
Specifies the action performed. For rate limiting checks, this
value is check. |
status |
Indicates whether the request was allowed or denied. |
key |
Specifies the subject key used for rate limiting. This can represent a client, a session, or a global bucket. |
reason |
Provides the reason for denial when applicable. For example,
rate_limit. |
client_id or session_id |
Specifies the identifiers for the client or session, if available from the FastMCP context. |
Use structured logging to ensure audit events can be parsed consistently and integrated with monitoring tools.