0.10.0 uses log4j2. Look under log4j2 directory and your will find a worker.xml file or something to that effect. In there you can define the output. Keep in mind that this will affect all topologies in that supervisor.
On Feb 29, 2016, at 13:52, Stephen Powis <[email protected]<mailto:[email protected]>> wrote: Hey! I recently upgraded to Storm 0.10.0 (and log4j as a result). I've noticed that topologies no longer log into worker-<workerid>.log and instead into a file named <topologyid>-worker-<workerid>.log I was curious as to if there's a way to control what the name of this log file is. I've tried adding a topology config item named "logfile.name<http://logfile.name>" but no luck. I must be missing something. Is there a way to hardcode the topology Id, or set this logfile to a static value on a per topology basis? Thanks!
