ICP runtime Id is not included in the metrics logs when ICP agent is running

[NipunaMadhushan]

Area

None

Description

ICP runtime ID is not included in the metrics logs even when ICP module is imported. However it is included in the application logs.

application log -

time=2026-01-31T22:50:38.475+05:30 level=INFO module=nipunal/test_icp_tags message="Fetching product list" icp.runtimeId="test123"

metric log -

time=2026-01-31T23:18:33.753+05:30 level=INFO module=ballerinax/metrics.logs message="" logger="metrics" protocol="http" listener.name="http" http.status_code_group="2xx" http.url="/shop/products" src.position="main.bal:46:5" entrypoint.resource.accessor="get" src.resource.path="/products" src.service.resource="true" src.module="nipunal/test_icp_tags:0.1.0" src.resource.accessor="get" src.object.name="Shopping Service" entrypoint.function.name="/products" entrypoint.service.name="Shopping Service" entrypoint.function.module="nipunal/test_icp_tags:0.1.0" http.method="GET" response_time_seconds="0.059787166"

Steps to Reproduce

Add the following imports to your Ballerina application.

import anuruddha/wso2.icp as _;
import ballerinax/metrics.logs as _;

Then add the following runtime configurations to your Ballerina application.

[ballerina.observe]
metricsLogsEnabled = true
 
[anuruddha.wso2.icp]
integration="sample-integration"
project="sample-project"
environment="dev"
heartbeatInterval=10

Version

Ballerina 2201.13.1

Environment Details (with versions)

No response

[NipunaMadhushan]

We can can access observability tags from the following API in ballerina/observe module.

string? runtimeId = observe:getTagValue("icp.runtimeId");

We get the tag value from the current observer context in the Ballerina runtime. When there are no any observable function or a resource/remote function is running, observer context in null. Therefore we cannot access even default obervability tags.

However this is required since we need to add ICP runtime id in the logs in order to filter them based on the id.

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.