> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/features/monitoring-and-reporting.md). # Monitoring and Reporting The platform continuously monitors API availability, performance and usage. It provides regulator-ready metrics and role-specific operational reports. ## XS2A Performance dashboard The **XS2A Performance dashboard** publishes the availability and performance statistics required for PSD2 fallback-exemption monitoring. It is available through the [Developer Portal](/portals-and-interfaces/developer-portal.md) for third parties and supervisors. {% hint style="info" %} All metrics are calculated in full compliance with the European Banking Authority (EBA) requirements. {% endhint %} The dashboard covers uptime, downtime, error rates and response times. It retains daily data and supports tenant-level or aggregated views. Metrics use real gateway traffic. Optional synthetic probes provide measurements during low-traffic periods. ## Operational reports Reports provide each audience with the information relevant to its responsibilities: * **Platform operators** track platform-wide API volumes, tenant usage, errors and billing. * **Banks** review third-party traffic, consent activity, fees, interface performance and creditor-account patterns. * **Third-party providers** review their API usage, performance and product fees, separately for sandbox and production. ## Audit trail Every API exchange is captured in a long-term audit store, such as Elasticsearch or OpenSearch. Asynchronous message processing keeps auditing outside the API call path. Records share a trace identifier. Sensitive data is masked under the audit policy. Retention varies by record type, while older data moves to cold storage and remains searchable. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.api.tieto.com/features/monitoring-and-reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.