I have to write a technical justification for a customer, in regards to the 777 permissions, especially in the dynatrace log directory. They would like to change it and lock it down but base on experience and from documentation, I know that this is not recommended. I came up with this, anybody has any inputs to this?
"In regard to the 777 permissions visible in certain Dynatrace directories (especially the log directory within the dynatrace install directory), at this point in time there is no recommended way (or supported way) to lock all those directories down. One reason is, that at the time of instrumenting, you do not know yet all the processes that OneAgent will be injected into when Full Stack mode is turned on, neither do you know what users those potential processes are running as. The user under which potential apps or processes that are being instrumented are running, will actually be the user that writes into those directories, hence, if that user would not have the proper permissions, no logs could be written, and certain procedures, such as the health check, will fail. Hence, these directories must be world writeable to ensure that every needed process will always be able to write into them.
Another reason is to ensure that every instrumented process will be able to write data into certain log directories (e.g. the crash report directory) since the instrumented processes do not run as the dtuser (or whatever user you have used when you installed OneAgent). Instrumentation may on occasion fail and not produce the expected outcome if those directory permissions are changed.
Also note that these directories are log directories, by definition, Dynatrace does not place any sensitive information into these directories, and there is no way to compromise the system by modifying files and content within those directories.
Modifying these permissions will potentially stop Dynatrace from investigating errors and incidents on OneAgent, â– â– â– logs that cannot be written because of permission issues, will be missing. Same goes for utilities such as the health check, that will fail when detecting unsupported permission sets."
Any comments welcome ![]()