Add logging showcase by ShivamPatidar24 · Pull Request #267 · eclipse-score/reference_integration

ShivamPatidar24 · 2026-06-19T05:05:15Z

Summary

This PR adds a Logging example showcase demonstrating local and remote logging.

The example generates logs for all supported severity levels.

This PR Depends on : #281

Verification
DEBUG, INFO, WARN, ERROR and FATAL logs generated
Logs visible in console output
Logs visible in DLT Viewer and Chipmunk

github-actions · 2026-06-30T10:29:47Z

The created documentation from the pull request is available at: docu-html

Signed-off-by: Cvam7 <108720572+ShivamPatidar24@users.noreply.github.com>

tejaswinijoshi89 · 2026-07-01T08:47:02Z

+                    "//patches/logging:001-logging-example-visibility.patch",
+                    "//patches/logging:002-deps-visibility.patch"],
                "metadata": {
+                    "code_root_path": "//score/mw/...",


Score/datarouter and other coding folders (if any) from logging cannot be skipped from code root path

rmaddikery · 2026-07-07T08:19:38Z

@@ -0,0 +1,13 @@
+diff --git a/MODULE.bazel b/MODULE.bazel


the patch file name and the patch (intent) does not match.

rmaddikery · 2026-07-07T08:20:44Z

+
+ # OCI / Docker image rules for integration tests
+ bazel_dep(name = "rules_oci", version = "2.2.7", dev_dependency = True)
+-bazel_dep(name = "rules_pkg", version = "1.2.0", dev_dependency = True)


Instead why not load it in reference_integration directly? IS the dep not allowed in ref_integration?

Without the patch, the build fails with a rules_pkg visibility error. Adding rules_pkg to the root MODULE.bazel results in a duplicate bazel_dep error.

rmaddikery · 2026-07-07T08:27:47Z

@@ -0,0 +1,27 @@
+{
+    "name": "Logging example",
+    "description": "Example for running logging with all log levels via remote and console",


Suggested change

"description": "Example for running logging with all log levels via remote and console",

"description": "A Logging app that demonstrates logging with mw::log with kConsole|kRemote|kFile config.",

rmaddikery · 2026-07-07T08:28:00Z

@@ -0,0 +1,27 @@
+{
+    "name": "Logging example",


Suggested change

"name": "Logging example",

"name": "LoggingApp Demo",

rmaddikery · 2026-07-07T08:29:46Z

@@ -0,0 +1,7 @@
+# Logging Example
+
+This example demonstrates logging with all log levels via Console Logging and Remote Logging.


Suggested change

This example demonstrates logging with all log levels via Console Logging and Remote Logging.

This Logging App demonstrates logging using mw::log with all log levels and configured backends (kConsole|kRemote|kFile) enabled.

rmaddikery · 2026-07-07T08:30:43Z

+
+This example demonstrates logging with all log levels via Console Logging and Remote Logging.
+
+For remote logging details, refer to the following documentation:


Suggested change

For remote logging details, refer to the following documentation:

For remote (DLT) logging, please refer to the following documentation:

rmaddikery · 2026-07-07T08:43:47Z



-def test_remote_logging(datarouter_running, dlt_config):
+def test_remote_logging(datarouter_running, target, dlt_config):


The test here verifies if datarouter logs are available in DLT. You should add another assert statement verifying if the Logging App logs end up in DLT. I would suggest adding a seperate test for this to seperate the expectations. E.g.:

# Verifies logging app logs are forwarded to DLT by capturing DLT traces
def test_logging_app_logs_forwarded_to_dlt(datarouter_running, target, dlt_config):

rmaddikery

https://github.com/eclipse-score/reference_integration/pull/267/changes#r3534900206

The verification should be showcased in the Test and NOT manually!

Co-authored-by: Raghavendra Maddikery <raghav.maddikery@gmail.com> Signed-off-by: Cvam7 <108720572+ShivamPatidar24@users.noreply.github.com>

ShivamPatidar24 added 2 commits June 19, 2026 10:19

ref_int : add logging and DLT generator showcase examples

a74eafe

logging: update hash and add patches

38c3c66

ShivamPatidar24 force-pushed the add_logging_showcase branch 9 times, most recently from 67795eb to 5591382 Compare June 26, 2026 05:08

ShivamPatidar24 force-pushed the add_logging_showcase branch 6 times, most recently from ee0df41 to 5cb2f27 Compare June 30, 2026 09:32

ShivamPatidar24 force-pushed the add_logging_showcase branch 4 times, most recently from 7fdfb65 to 38c3c66 Compare July 1, 2026 07:04

ShivamPatidar24 and others added 3 commits July 1, 2026 12:47

integrate logging example

08a09b7

Merge branch 'main' into add_logging_showcase

f8aa77e

Signed-off-by: Cvam7 <108720572+ShivamPatidar24@users.noreply.github.com>

fix format

a3dbfe4

tejaswinijoshi89 suggested changes Jul 1, 2026

View reviewed changes

update README

af21cd1

ShivamPatidar24 marked this pull request as ready for review July 1, 2026 10:33

ShivamPatidar24 requested review from PiotrKorkus and pawelrutkaq as code owners July 1, 2026 10:33

ShivamPatidar24 requested review from AlexanderLanin, FScholPer, MaximilianSoerenPollak, antonkri, dcalavrezo-qorix, lurtz, nradakovic and opajonk as code owners July 1, 2026 10:33

rmaddikery reviewed Jul 7, 2026

View reviewed changes

Comment thread showcases/README.md Outdated

rmaddikery reviewed Jul 7, 2026

View reviewed changes

rmaddikery requested changes Jul 7, 2026

View reviewed changes

ShivamPatidar24 force-pushed the add_logging_showcase branch 2 times, most recently from ac3e99b to 9f49a98 Compare July 9, 2026 10:15

logging: address review comments

2cb51e4

Co-authored-by: Raghavendra Maddikery <raghav.maddikery@gmail.com> Signed-off-by: Cvam7 <108720572+ShivamPatidar24@users.noreply.github.com>

ShivamPatidar24 force-pushed the add_logging_showcase branch from 9f49a98 to 2cb51e4 Compare July 9, 2026 10:35

	"description": "Example for running logging with all log levels via remote and console",
	"description": "A Logging app that demonstrates logging with mw::log with kConsole\|kRemote\|kFile config.",

		@@ -0,0 +1,7 @@
		# Logging Example

		This example demonstrates logging with all log levels via Console Logging and Remote Logging.

	This example demonstrates logging with all log levels via Console Logging and Remote Logging.
	This Logging App demonstrates logging using mw::log with all log levels and configured backends (kConsole\|kRemote\|kFile) enabled.


		This example demonstrates logging with all log levels via Console Logging and Remote Logging.

		For remote logging details, refer to the following documentation:

	For remote logging details, refer to the following documentation:
	For remote (DLT) logging, please refer to the following documentation:



		def test_remote_logging(datarouter_running, dlt_config):
		def test_remote_logging(datarouter_running, target, dlt_config):

Uh oh!

Conversation

ShivamPatidar24 commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jun 30, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rmaddikery Jul 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rmaddikery Jul 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rmaddikery left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

ShivamPatidar24 commented Jun 19, 2026 •

edited

Loading

rmaddikery Jul 7, 2026 •

edited

Loading

rmaddikery Jul 7, 2026 •

edited

Loading

rmaddikery left a comment •

edited

Loading