question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change log statements to Debug instead of Info.

See original GitHub issue

This seems to be a recurrence of the issue outlined in #219

I am getting this kind of stuff in my logs using Glass.Mapper 4.3.4.196 on Sitecore 8.2 - Update 2.

This is a ton of noise when I am trying to address other issues.

1920 07:45:39 INFO GetModelFromView 0 {25363DC2-49BC-4FB9-84FF-F9164BE6CC3E}
1920 07:45:39 INFO GetModelFromView 0 {25363DC2-49BC-4FB9-84FF-F9164BE6CC3E}
1920 07:45:39 INFO GetModelFromView 0 {25363DC2-49BC-4FB9-84FF-F9164BE6CC3E}
1920 07:45:39 INFO GetModelFromView 0 {54661361-3C46-4AAA-A82B-6D649F43917F}
1920 07:45:39 INFO GetModelFromView 0 {1B427610-DB06-4F5B-AD35-8F1E8B8FD56B}
6720 07:45:39 INFO GetModelFromView 0 {FE5D7FDF-89C0-4D99-9AA3-B5FBD009C9F3}
6720 07:45:39 INFO GetModelFromView 0 {9DC3117B-367E-4510-AB61-490DDC8359A5}
6720 07:45:39 INFO GetModelFromView 0 {FD8ED973-34E5-4544-9886-9269BA4C1227}
6720 07:45:39 INFO GetModelFromView 0 {729DA297-DB63-4362-B835-E3D4E0CC90E5}
6720 07:45:39 INFO GetModelFromView 0 {AF675ECD-84AC-4110-A334-EB1CA2A34452}
6720 07:45:39 INFO GetModelFromView 0 {25363DC2-49BC-4FB9-84FF-F9164BE6CC3E}
6720 07:45:39 INFO GetModelFromView 0 {5281E350-9958-457F-8D37-FD98134FC9A4}
1920 07:45:40 INFO GetModelFromView 0 {9D5CCD1F-4519-4633-BDFE-72AC41131609}
1920 07:45:41 INFO GetModelFromView 0 {25363DC2-49BC-4FB9-84FF-F9164BE6CC3E}
1920 07:45:41 INFO GetModelFromView 0 {5281E350-9958-457F-8D37-FD98134FC9A4}

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
mikeedwards83commented, Feb 19, 2017

I hadn’t realised that you had issued a pull request. I have fixed as part of #285

0reactions
n-developcommented, Jun 29, 2017

Is this included in any official version already?

Read more comments on GitHub >

github_iconTop Results From Across the Web

change log4j Logging level from INFO to DEBUG
Hibernate messages it self is in hibernate source code, you can't change that. However, you can change Hibernate log level to warn or...
Read more >
Stop Using “Print” and Start Using “Logging”
A better way to track your code events and do debugging is using the “Logging” library (a Python standard library). The logging library...
Read more >
Log Levels Explained and How to Use Them
The DEBUG level is used for logging messages that aid developers in identifying issues during a debugging session. The content of the messages...
Read more >
Logging Levels: What They Are & How to Choose Them
A log level used for events considered to be useful during software debugging when more granular information is needed.
Read more >
Why does the TRACE level exist, and when should I use it ...
They warrant a separate TRACE level rather than just using DEBUG because enabling ENTRY/EXIT logs for every method in your code base is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found