Install the chrome event log provider together with the browser.

chrome/installer/setup/setup_util.cc

Index: chrome/installer/setup/setup_util.cc
diff --git a/chrome/installer/setup/setup_util.cc b/chrome/installer/setup/setup_util.cc
index 233287bf519375396cf4082baa66791711886c63..88c6d22aa2b00692ef240c59952ad8e4666038e1 100644
--- a/chrome/installer/setup/setup_util.cc
+++ b/chrome/installer/setup/setup_util.cc
@@ -11,6 +11,8 @@
 
 #include <algorithm>
 #include <iterator>
+#include <limits>
+#include <memory>
 #include <set>
 #include <string>
 
@@ -36,6 +38,7 @@
 #include "chrome/installer/setup/user_hive_visitor.h"
 #include "chrome/installer/util/app_registration_data.h"
 #include "chrome/installer/util/google_update_constants.h"
+#include "chrome/installer/util/install_util.h"
 #include "chrome/installer/util/installation_state.h"
 #include "chrome/installer/util/master_preferences.h"
 #include "chrome/installer/util/master_preferences_constants.h"
@@ -47,6 +50,10 @@ namespace installer {
 
 namespace {
 
+// Event log provider registry location and value names.
+constexpr wchar_t kEventLogProvidersRegPath[] =

[grt (UTC plus 2), 2016/11/18 11:38:12]

nit: kEventLogProviderRegPath

[pastarmovj, 2016/11/21 15:48:40]

Done.

+    L"\\SYSTEM\\CurrentControlSet\\Services\\EventLog\\Application\\chrome";

[grt (UTC plus 2), 2016/11/18 11:38:12]

can "chrome" be any string, or does it need to be "chrome"? as-is, multiple
installs will collide in this registry key (i.e., stable, dev, beta), as will
Chromium.

[grt (UTC plus 2), 2016/11/18 12:10:34]

Maybe use BrowserDistribution::GetBaseAppName() for the last component of this
path? It returns something different for each install.

[pastarmovj, 2016/11/21 15:48:40]

Unfortunately this has to coincide with the costant kEventSource defined here
https://cs.chromium.org/chromium/src/base/syslog_logging.cc?rcl=0&l=28 which is
in base and therefore would not be suitable to depend on other components. I
think however this is not a big deal since worst case a degraded UI experience
in the Event Viewer will appear but no crashes or anything will happen. 

[grt (UTC plus 2), 2016/11/22 10:41:25]

ah, this is pretty bad. any Chromium-based browser co-installed with Google
Chrome will use Chrome's log provider dll. i think we can do better. you could
introduce a function in logging:: to set the event source name, and then call it
from within Chrome somewhere after Chrome figures out which channel it is. each
Chrome channel should have its own event source name. it would be natural to add
the event source name to install_static/install_constants.h, and then in
chromium_install_modes.cc and google_chrome_install_modes.cc. you would then add
an accessor for it to InstallDetails (a la app_guid()). InitChromeLogging could
then set the event source name with something like:

 
logging::SetEventSourceName(install_static::InstallDetails::Get().event_source_name());

this scales better across multiple distributions. the installer can't use this
part of install_static until i land https://codereview.chromium.org/2459583002/,
so you would have to be a little hacky in here for now. add a TODO(grt) to clean
it up.

[grt (UTC plus 2), 2016/11/24 07:49:34]

Also anything else built using Chromium's base, which is a growing body of
software (CEF and whatnot).

+
 // Returns true if product |type| cam be meaningfully installed without the
 // --multi-install flag.
 bool SupportsSingleInstall(BrowserDistribution::Type type) {
@@ -660,6 +667,46 @@ void RecordUnPackMetrics(UnPackStatus unpack_status,
       ->Add(status);
 }
 
+void RegisterEventLogProvider(const base::FilePath& chrome_exe) {
+  VLOG(1) << "Registering Chrome's event log provider at "
+          << kEventLogProvidersRegPath;
+
+  std::unique_ptr<WorkItemList> work_item_list(WorkItem::CreateWorkItemList());
+
+  work_item_list->AddCreateRegKeyWorkItem(
+      HKEY_LOCAL_MACHINE, kEventLogProvidersRegPath, WorkItem::kWow64Default);
+  work_item_list->AddSetRegValueWorkItem(
+      HKEY_LOCAL_MACHINE, kEventLogProvidersRegPath, WorkItem::kWow64Default,
+      L"CategoryCount", static_cast<DWORD>(1), true);
+  work_item_list->AddSetRegValueWorkItem(

[grt (UTC plus 2), 2016/11/18 11:38:12]

nit: could you put a simple comment above each of these explaining what they
accomplish? what does "7" mean?

[pastarmovj, 2016/11/21 15:48:40]

Done.

+      HKEY_LOCAL_MACHINE, kEventLogProvidersRegPath, WorkItem::kWow64Default,
+      L"TypesSupported", static_cast<DWORD>(7), true);
+
+  base::FilePath provider(chrome_exe.DirName());
+  provider.Append(FILE_PATH_LITERAL("eventlog_provider.dll"));

[grt (UTC plus 2), 2016/11/18 11:38:12]

the provider is in the version directory, so you need to Append the version #
being installed, no? i think all callers of RegisterChromeOnMachine know the
version, so you could pass it on down into here.

[pastarmovj, 2016/11/21 15:48:40]

Done.

+
+  static constexpr wchar_t* file_keys[] = {
+      L"CategoryMessageFile",
+      L"EventMessageFile",
+      L"ParameterMessageFile",
+  };
+  for (const wchar_t* file_key : file_keys) {
+    work_item_list->AddSetRegValueWorkItem(
+        HKEY_LOCAL_MACHINE, kEventLogProvidersRegPath, WorkItem::kWow64Default,
+        file_key, provider.value(), true);
+  }
+
+  // if the operation fails we log the error but still continue because none of
+  // these are critical for the proper operation of the browser.
+  if (!work_item_list->Do())

[grt (UTC plus 2), 2016/11/18 11:38:12]

are you intentionally not calling Rollback? if so, please explain why in the
comment above. or is that what you're trying to convey in the comment?

[pastarmovj, 2016/11/21 15:48:41]

No sorry I mistakenly assumed that the rollback is the default behavior but now
I read what you were telling me is that I can change the default on a task by
task basis not that it will magically happen for the list.

+    LOG(ERROR) << "Could not register Chrome's event log provider.";
+}
+
+void DeRegisterEventLogProvider() {
+  InstallUtil::DeleteRegistryKey(HKEY_LOCAL_MACHINE, kEventLogProvidersRegPath,
+                                 WorkItem::kWow64Default);
+}
+
 ScopedTokenPrivilege::ScopedTokenPrivilege(const wchar_t* privilege_name)
     : is_enabled_(false) {
   HANDLE temp_handle;