Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NMS-17070 Log messages from Groovy are truncated #7637

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

Mohammad-Junid
Copy link
Contributor

Messages written to the Karaf log from a telemetry adapter groovy script appear to be truncated. How can I see the entire log message?

@Mohammad-Junid Mohammad-Junid marked this pull request as ready for review February 24, 2025 12:27
Copy link
Contributor

@cgorantla cgorantla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As this can be updated runtime, this can be a doc update here instead of updating directly here.

We should be able to update cfg file through config:edit org.ops4j.pax.logging pattern.

Please validate this through config update.

@dino2gnt
Copy link
Contributor

As this can be updated runtime, this can be a doc update here instead of updating directly here.

We should be able to update cfg file through config:edit org.ops4j.pax.logging pattern.

Please validate this through config update.

Why not BOTH?

christianpape
christianpape previously approved these changes Feb 26, 2025
Copy link
Contributor

@christianpape christianpape left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@cgorantla
Copy link
Contributor

cgorantla commented Feb 26, 2025

As this can be updated runtime, this can be a doc update here instead of updating directly here.
We should be able to update cfg file through config:edit org.ops4j.pax.logging pattern.
Please validate this through config update.

Why not BOTH?

This file is coming from Karaf, don't want to have a custom change which needs to be taken for every karaf upgrade. Don't need to change this unless it is really a must.

For this case, we are really not sure if 2000 is sufficient or not so even if we update this, won't take care of all cases.
Good enough to have a doc update.

Copy link
Contributor

@cgorantla cgorantla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only needs a doc update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants