Observability is the ability to measure and understand the internal state of a system based on the data it produces. It provides insight into how a system behaves under different conditions. It helps answer questions such as:
  • Is the system performing as expected?
  • Where are potential bottlenecks or failures occurring?
  • How can performance be improved?
Observability in the OpenEdge MCP Server includes three key components:
  • Logging—Captures system and application messages for troubleshooting and analysis.
  • Audit events—Records security and compliance-related activities.
  • Timing data—Tracks performance metrics and execution times for operations.
Here are the primary objectives for implementing observability. These objectives ensure that the data collected is useful, secure, and easy to interpret.
  • Provide actionable, low-noise telemetry—Collect meaningful data that supports security, performance, and usage analysis without overwhelming users with unnecessary details.
  • Enable flexible log formats—Allow easy switching between human-readable logs and structured logs that can be parsed by machines for automation and analysis.
  • Protect sensitive information—Prevent exposure of credentials such as service account tokens and private keys while maintaining sufficient traceability for troubleshooting and audits.