# cannot view old threads **URL:** \ **Category:** General\ **Tags:** question\ **Created:** [June 20, 2022, 12:01pm UTC](https://community.netdata.cloud/t/cannot-view-old-threads/3021 "2022-06-20T12:01:14Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![lupimiguel](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/lupimiguel/32/1304_2.png) [@lupimiguel](https://community.netdata.cloud/u/lupimiguel)\ **Post date:** [June 21, 2022, 1:29pm UTC](https://community.netdata.cloud/t/cannot-view-old-threads/3021/4 "2022-06-21T13:29:28Z")
Hi @ml35 how are you today? I’ve changed the category on your threads so you can see the replies. As @Tasos_Katsoulas mentioned, the feature requests category in the Forums was deprecated in favour of discussing them directly in the repositories, whether through an issue template or Github Discussions. > [@Make smartd\_log plugin also search /var/lib/smartmontools on ubuntu instead of failing when /var/log/smartd is missing](https://community.netdata.cloud/t/make-smartd-log-plugin-also-search-var-lib-smartmontools-on-ubuntu-instead-of-failing-when-var-log-smartd-is-missing/1627): > > ubuntu smartd version 6.5+svn4324-1ubuntu0 and later (ubuntu 18.04 and newer) does not run with -A but still writes metrics into /var/lib/smartmontools csv files it would be useful to make the plugin also search for this path instead of the default /var/log/smartd, which would allow smartd support out of the box from ubuntu 18.04 man page -A PREFIX, --attributelog=PREFIX If this option is not specified, attribute information is written to files ´/var/lib/smartmontools/attrlog.MODEL-… > [@False alarms detection](https://community.netdata.cloud/t/false-alarms-detection/1607): > > I get flooded with false alarms. I spend a lot of time adjusting the thresholds but I never get the perfect setup. I am thinking how to reduce the number of alarms. Using solely the threshold criteria is not enough and sometimes even misleading! For example, a 10min\_disk\_backlog of 5000ms is perfectly expected on a server that does some work it was designed for, but a 200ms on the same server when idle it would indicate a hardware disk issue. Setting the threshold at 6000ms would eliminate the… Let me know if we can help with anything else, thank you for your contributions and have a nice day! --- _[View the full topic](https://community.netdata.cloud/t/cannot-view-old-threads/3021)._