Make the name of the event source for SYSLOG configurable.

chrome/common/logging_chrome.cc

Index: chrome/common/logging_chrome.cc
diff --git a/chrome/common/logging_chrome.cc b/chrome/common/logging_chrome.cc
index 183d4e84792abcfdcc0c4764a51600653d4f6504..584c5204a8d906f7ab34cef444ff8b3c579a6551 100644
--- a/chrome/common/logging_chrome.cc
+++ b/chrome/common/logging_chrome.cc
@@ -61,6 +61,8 @@
 #if defined(OS_WIN)
 #include <initguid.h>
 #include "base/logging_win.h"
+#include "base/syslog_logging.h"
+#include "chrome/install_static/install_modes.h"
 #endif
 
 namespace {
@@ -359,6 +361,10 @@ void InitChromeLogging(const base::CommandLine& command_line,
 #if defined(OS_WIN)
   // Enable trace control and transport through event tracing for Windows.
   logging::LogEventProvider::Initialize(kChromeTraceProviderName);
+
+  // Enable logging to the Windows Event Log.
+  logging::SetEventSourceName(
+      base::UTF16ToASCII(install_static::kProductPathName));

[grt (UTC plus 2), 2016/11/25 15:25:35]

while this will be a brand-specific string (e.g., "Chromium" or "Chrome"), what
we need here is a "mode"-specific string to account for a product being
installed in multiple side-by-side locations (e.g., "Chrome SxS" or "Chrome
Beta" vs "Chrome"). i propose that you add a new member to
install_static::InstallConstants for the log event source name and add values
for it to the kInstallModes definitions in chromium_install_modes.cc and
google_chrome_install_modes.cc. you can then add a convenience getter to
InstallDetails that you call here.

[pastarmovj, 2016/11/28 12:23:03]

I am not convinced that this particular use case deserves splitting up at such
fine granularity. But the code needed to achieve it is not much and we can
rather do this now than later.

I decided to go for a more generic install_full_name() rather than a specific to
this case name. WDYT?

 #endif
 
   base::StatisticsRecorder::InitLogOnShutdown();