---
title: Logging & Monitoring
slug: logging-and-monitoring
docTags: 
createdAt: 2026-07-07T17:38:20.484Z
---

The Kyndryl Bridge Logging Service provides a common logging experience in Kyndryl Bridge by surfacing application and runtime logs through a shared Grafana-based dashboard. It enables application developers, SREs and operations teams to efficiently access service logs from within Bridge for troubleshooting and analysis. The Grafana observability stack is a lift-and-shift implementation of the AIOps logging stack within Bridge.&#x20;

The Kyndryl Bridge Grafana sync service automatically creates new Grafana organizations whenever new Kyndryl Bridge tenants (accounts) are onboarded, ensuring account-level segregation within Grafana dashboards. The service also adds users to the appropriate organizations based on Kyndryl Bridge permissions.&#x20;

The following capabilities extend the existing logging experience for users:&#x20;

- Provides a common logging experience for Kyndryl Bridge apps and services through a shared Grafana-based dashboard.&#x20;
- Provides Kyndryl Bridge UI entry points to display application and runtime logs from within Bridge.&#x20;
- Automatically creates dedicated Grafana organizations for newly onboarded Kyndryl Bridge tenants to support account-level segregation.&#x20;
- Integrates with Kyndryl Bridge roles,**&#x20;IA** and **SSO** to provide governed access to logging dashboards.&#x20;
- Supports context-aware log access based on the selected Kyndryl Bridge account or tenant, ensuring users can view only the log data they are authorized to access.&#x20;
- Users can filter logs by service to support faster issue of isolation and debugging.&#x20;
- If services want to display logs in a specific format, such as starting with a **tenant ID&#x20;**&#x61;nd the **Bridge Logging Service&#x20;**&#x63;an support that.&#x20;
- Supports log download for offline analysis.&#x20;
- Logs are retained in Grafana for a period of **30 days**.&#x20;
- Logs are retained through container restarts and can be queried across restarts. For example, if a pod is deleted and recreated, logs from both the old and new pods can still be queried.&#x20;
- Supports bot&#x68;**&#x20;redacted&#x20;**&#x61;nd **unredacted logs**. For example, sensitive data such as IP addresses and email addresses can be redacted.&#x20;

# Access Logging & Monitoring&#x20;

Use Logging & Monitoring to access the **Logs** dashboard, monitor system activity and troubleshoot issues through Grafana-based observability tools. Follow these steps to access Loggin & Monitoring:&#x20;

From the Kyndryl Bridge main menu :inlineImage[]{src="https://api.archbee.com/api/optimize/QU1TIK52ntw5Jsos0uOt5/NK7Yw9tQgnlqBGwu7eG4H-20260601-205917.svg" alt caption width="57" height="57"}, go to  **Administration** → **Service Operations** → **Logging & Monitoring**.&#x20;

Access to the Logging & Monitoring service is available t&#x6F;**&#x20;App Developers** and **Delivery/Operations&#x20;**&#x75;sers with the **Platform Admin or Platform Viewer&#x20;**&#x72;ole. Available features and log visibility are limited to authorized Bridge accounts and tenants based on assigned permissions:&#x20;

- **Platform Admin:&#x20;**&#x50;latform Admins can view, download and manage logs, including access to redacted logs and the ability to switch between applications. These permissions are assigned to Admin platform roles.
  - Observability.logs.view
  - Observability.redactedlogs.view
  - Observability.logs.download
  - Observability.logs.switchapps
- **Platform Viewer:** Platform Viewers can switch between applications and view logs, including redacted logs, and can download logs when permitted. These permissions are assigned to platform viewers:
  - Observability.logs.view
  - Observability.redactedlogs.view
  - Observability.logs.download
  - Observability.redactedlogs.view

# Log data retention

Although log data is retained for a maximum of **30 days&#x20;**&#x61;nd automatically deleted after the retention period, a key capability of the logging service is that logs remain available even if pods restart. This helps preserve log history across application lifecycle events and supports troubleshooting without losing log data due to pod restarts.

# Download logs

The platform admin would be able to download the logs in plain text (txt) or JSON format.
