Screen Shot 2012-11-01 at 10.53.56 AM.png
[MB-7075] Mac/OSX drop-down UI menu points to different log location Created: 01/Nov/12 Updated: 05/Nov/12 Resolved: 05/Nov/12 |
|
| Status: | Closed |
| Project: | Couchbase Server |
| Component/s: | UI |
| Affects Version/s: | 2.0 |
| Fix Version/s: | None |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Don Pinto | Assignee: | Jens Alfke |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | Only tested on MacOS | ||
| Attachments: |
Screen Shot 2012-11-01 at 10.53.56 AM.png
|
| Description |
|
logs on Mac OS are available under ~/Library/Application Support/Couchbase/var/lib/couchbase/logs but when clicking the "show logs" in the UI, we don't go to this path (we goto Couchbase.log under ~/Library/Logs)
|
| Comments |
| Comment by Steve Yen [ 02/Nov/12 ] |
|
updated title
|
| Comment by Steve Yen [ 02/Nov/12 ] |
|
Options discussed in bug-scrub...
- remove the drop-down menu entry for View Logs. - fix the View Logs choice. Whatever's easier/less-intensive/less-riskier. Yaseen to followup with Jens -- leaving open, although not a blocker, per bug-scrub mtg |
| Comment by Jens Alfke [ 02/Nov/12 ] |
|
~/Library/Logs/Couchbase.log *is* a valid log file that the server writes to. I've used it to diagnose Erlang exceptions launching the server. But it sounds like it's less important than the ones in the App Support folder?
Changing the app to open a different log file is trivial; even easier than taking out the command. However, that log directory has a lot of files in it. Unfortunately the Console app can't be told to view a directory, just an individual file. So the choices would be: (a) Pick a single file in 'logs' to open, if one of them is more important. (b) Make a submenu with items for all the significant log files (c) Make the menu command open the logs folder itself in the Finder (not terribly useful, because most of the files don't have filename extensions that indicate that they're text, so double-clicking them doesn't work.) |
| Comment by Steve Yen [ 02/Nov/12 ] |
|
I'd vote for (a), and please check with alk on which one's the right one.
Option (b), might be "brittle", depending on how you do it. That is, if we change the logging files again in the server, it could be yet-another thing to fix in the future. |
| Comment by Farshid Ghods [ 03/Nov/12 ] |
|
i also vote for option (a)
there are many files in that folder and if user needs to collect diagnostics they use cbcollect info command anyways. |
| Comment by Steve Yen [ 05/Nov/12 ] |
|
in bug-scrub mtg...
option (d) - (alk proposes) pipe output of cbbrowse-logs to some window option (e) - remove this menu item and document the cbbrowse-logs command option (e) is the final bug-scrub mtg choice. |
| Comment by Jens Alfke [ 05/Nov/12 ] |
|
Removed the menu command from the UI. (No code change, just deleted the menu item from the nib.)
Out for review: http://review.couchbase.org/#/c/22280/ |
| Comment by Steve Yen [ 05/Nov/12 ] |
| Thanks Jens - resolving this as your fix was submitted past gerrit. |
| Comment by Farshid Ghods [ 05/Nov/12 ] |
| verified with build 1941 |