# How to get generated specific log files under DEFAULT path (e.g. notice.log)
**URL:** https://community.zeek.org/t/how-to-get-generated-specific-log-files-under-default-path-e-g-notice-log/5129
**Category:** Zeek
**Created:** [December 16, 2017, 7:59am UTC](https://community.zeek.org/t/how-to-get-generated-specific-log-files-under-default-path-e-g-notice-log/5129 "2017-12-16T07:59:30Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Zick\_Zack](https://community.zeek.org/u/Zick_Zack)
#### Post date: [December 16, 2017, 7:59am UTC](https://community.zeek.org/t/how-to-get-generated-specific-log-files-under-default-path-e-g-notice-log/5129/1 "2017-12-16T07:59:30Z")
Hi Bro’ers
I have a problem to get generated a notice.log file with it’s DEFAULT path.
Short description of my problem:
- whenever I start Bro to do sth., I get generated some log-files (e.g. communication, http, …) in a folder named /var/log/bro
- however (also after a “deploy” command!), when I call e.g. “NOTICE([$note=_ **, $msg="** _”])", I get NOT generated a notice.log file ANYWHERE on my VM
- I can somehow circumvent that by manipulating the share/bro/base/frameworks/notice/main.bro file, when I explicitly set the $path variables in there to my absolute path like “/var/log/bro/notice”
Some background I already found out:
- it is said in the Bro documentation NOT to change any files in the directories (and its sub-folders) from share/bro EXCEPT the share/bro/site-folder
- I found out, all the modules for which the DEFAULT path log-file generation is working somehow load (directly or indirectly) the base/utils/paths or the base/utils/site modules
What I want:
- getting generated my notice.log file without specifiying an absolute path; only the file-name (just like as it works for the other log files in my /var/log/bro folder)
Please help me to get my notice.log file WITHOUT manipulating files which one should not touch!
Thanks alot in advance!
---
### Author:  [@johanna](https://community.zeek.org/u/johanna)
#### Post date: [January 26, 2018, 5:41pm UTC](https://community.zeek.org/t/how-to-get-generated-specific-log-files-under-default-path-e-g-notice-log/5129/2 "2018-01-26T17:41:08Z")
Hi,
did you randomly already find a solution for this in the meantime? Just
from reading over this, I am a bit at a loss for why this would happen.
Basically - the on-disk-files are created the first time that something is
written into then. So - it is normal that a notice.log might not show up
immediately. However, it should show up after you call NOTICE.
It is a bit weird that it would work after you put a full path into
notice/main - I am not sure why this would change anything.
How exactly did you try to generate your test notice? Note that if you are
using cluster mode, a NOTICE in bro\_init() will probably not show up in
notice.log due to the fact that the logging connections are not set up yet
when it is raised.
Also - what Bro version are you using?
Johanna
---
### Author:  [@system](https://community.zeek.org/u/system)
#### Post date: [May 6, 2022, 3:45pm UTC](https://community.zeek.org/t/how-to-get-generated-specific-log-files-under-default-path-e-g-notice-log/5129/3 "2022-05-06T15:45:28Z")