Re:How 'DevOps' is Killing the Developer (2014)
by mhaymo on Monday August 31, 2015 @05:18AM
(#10146052)
To my mind the whole point of DevOps is to make the developers "get it" by making them feel the pain when they get things wrong. Developers make decisions about the system every day, so it pays for them to understand how it is maintained and operated.
Re:How 'DevOps' is Killing the Developer (2014)
by digi_owl on Monday August 31, 2015 @09:13AM
(#10146619)
My impression is that devops instead has turned into a means for getting sysadmins out of the way so developers can use the latest shiny in production...
Re:How 'DevOps' is Killing the Developer (2014)
by glenjamin on Monday August 31, 2015 @04:35AM
(#10145973)
Out of interest, why wouldn't you configure logrotate on the machine itself, rather than making this an application concern?
Presumably logrotate was already set up for the variety of other logs on the system?
Re:How 'DevOps' is Killing the Developer (2014)
by icebraining on Monday August 31, 2015 @04:37AM
(#10145980)
I was curious too, though it seems log4j just keeps writing to the old log (it doesn't re-open the file on SIGHUP), and copytruncate is not completely safe from data loss.
Re:How 'DevOps' is Killing the Developer (2014)
by einrealist on Monday August 31, 2015 @04:36AM
(#10145977)
Did they own the systems their applications were deployed to? Because that is the essence of full stack development. Otherwise, config management is required as boundary context between developers and operations.
Re:How 'DevOps' is Killing the Developer (2014)
by HelloNurse on Monday August 31, 2015 @09:09AM
(#10146611)
This only proves your Java developers were stupid and arrogant; using RollingFileAppender or something even smarter would be the norm in any sufficiently functional organization, regardless of whether developers anticipate the need or sysadmins need to ask.
Only the sysadmins "got it" because they were the ones that got to feel the pain of cleaning up a NAS filled up by log files.