<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Rainbow Dash Network</provider_name>
 <provider_url>http://rainbowdash.net/</provider_url>
 <title>adiwan (adiwan)'s status on Thursday, 04-Sep-25 12:24:49 UTC</title>
 <author_name>adiwan (adiwan)</author_name>
 <author_url>http://rainbowdash.net/adiwan</author_url>
 <url>http://rainbowdash.net/notice/5484168</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://rainbowdash.net/user/30324&quot; class=&quot;url&quot; title=&quot;Cerulean Spark&quot;&gt;&lt;span class=&quot;fn nickname mention&quot;&gt;ceruleanspark&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; Ah... Makes sense. At a project I was working on they had similar issues. They logged EVERYTHING and had space issues in production. So much so that they had to make rotating logs but soon after so much was logged that the rotating logs would only save about 2-3 hours and yet more and more logging was added. My code had also very verbose logging that could be disabled but the client wanted even that output all the time. Coincidentally their DB views got so big that certain joints in some applications suddenly stopped working because it had too many columns. It was quite the ordeal to debug that.</html>
</oembed>
