Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Logging in 10.2 loglines are truncated afterlittle more than 5000 characters : how to avoid that ?

Solved669 views6th June 2024
2
Cristel Van Landeghem [DevOps Advocate]468 29th March 2024 0 Comments

In Debug level we want to know exact the json contents that came in.  Sometimes it is much more than 5000 characters.

Previously this was no problem at all.

Now we have installed 10.2, and in there lines > 5000 characters are only written partialy written to the logfile => unusable for debugging.

How can we change this unwanted behaviour in 10.2 ?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 6th June 2024

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
2
Wouter Demuynck [SLC] [DevOps Advocate]5.93K Posted 3rd April 2024 0 Comments

Hi Cristel,

The 5K limit for loglines has been added for very good reasons, including process crashes on huge loglines and the inability to still see other loglines in between larger ones. It is a general protection against rogue logging. The 5K limit is a good compromise which protects the system while still allowing relatively large messages to be logged in case of need.

Some alternatives approaches could include:

  • Writing into a separate file aside from the protocol.Log method, e.g. using File.AppendAllText
  • Creating a debug textbox parameter in the driver in which the data is dumped, so you can inspect it afterwards
  • Writing chunks in a loop (as previously suggested), if the logging really needs to end up in the element logfile
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 6th June 2024
You are viewing 1 out of 2 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin