Log the analysis options path.

Log the analysis options path.

BUG=

[devoncarew, 2017-05-26 22:18:49]

devoncarew@google.com changed reviewers:
+ brianwilkerson@google.com, paulberry@google.com

[devoncarew, 2017-05-26 22:18:49]

This CL writes the analysis options location to the analysis server's print()
output. With regular runs, the location is written to the diagnostic output
(which is available from the analysis server's diagnostics page). When run from
the command-line with `--internal-print-to-console` this displays the analysis
options location to stdout.

We have additional options in terms of logging, if we want to investigate that,
including adding a general logging mechanism to the analysis server and an
associated analysis server API log notification. Not clear if that amount of
architecture is worth it just for this use case, but perhaps good for general
future uses.

[devoncarew, 2017-05-26 22:18:50]

This CL writes the analysis options location to the analysis server's print()
output. With regular runs, the location is written to the diagnostic output
(which is available from the analysis server's diagnostics page). When run from
the command-line with `--internal-print-to-console` this displays the analysis
options location to stdout.

We have additional options in terms of logging, if we want to investigate that,
including adding a general logging mechanism to the analysis server and an
associated analysis server API log notification. Not clear if that amount of
architecture is worth it just for this use case, but perhaps good for general
future uses.

[Paul Berry, 2017-05-26 22:27:52]

lgtm

[Brian Wilkerson, 2017-05-27 04:20:26]

I suppose what you have is fine, but it seems like if you want it on the status
pages it would be better to just display it on the "Context" page under
"Configuration" (without having to search through the print output).

Also, we could add an entry to the instrumentation log each time we create a
context / driver, which could indicate the root of the context, excluded
directories, the options file location, the URI resolvers, etc. That would seem
to be an easier way to capture the information.

[devoncarew, 2017-05-27 18:01:02]

On 2017/05/27 04:20:26, Brian Wilkerson wrote:
> I suppose what you have is fine, but it seems like if you want it on the
status
> pages it would be better to just display it on the "Context" page under
> "Configuration" (without having to search through the print output).

I wasn't entirely sure how to plumb the information through, and this seemed to
parallel what we're doing on the cli. I have some work now to add the options
path to the diagnostics page - I'll put that up for review.

[devoncarew, 2017-05-31 01:14:00]

Description was changed from

==========
Log the analysis options path.

BUG=
==========

to

==========
Log the analysis options path.

BUG=
==========