Add logging to remote commands

base/chromeos/logging.h

+// Copyright (c) 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef BASE_CHROMEOS_LOGGING_H_
+#define BASE_CHROMEOS_LOGGING_H_
+
+#include "base/logging.h"
+
+namespace logging {
+
+#if defined(OS_CHROMEOS)
+
+// These macros are used to log events on ChromeOS which we want to be included
+// in the system log of the device.
+#define CHROMEOS_SYSLOG(severity) LOG(severity)

[Nico, 2016/06/04 01:25:00]

Do you need separate severities for syslog entries? From what you described, it
sounded like the syslog is just a single file -- maybe this could always log at
a fixed level (say INFO, or what have you), then people don't have to decide on
a warning level when they want to use this?

[Marton Hunyady, 2016/06/06 08:28:54]

I think it's better to separate the failures (e.g. we couldn't upload) from
status (e.g. we started uploading). The system log uploaded to the admins
contains the log levels.

+#define CHROMEOS_SYSLOG_IF(severity, condition) LOG_IF(severity, condition)
+
+#else  // Not defined(OS_CHROMEOS)
+
+#define CHROMEOS_SYSLOG(severity) LOG_IF(severity, false)
+#define CHROMEOS_SYSLOG_IF(severity, condition) LOG_IF(severity, false)
+
+#endif  // defined(OS_CHROMEOS)
+
+}  // namespace logging
+
+#endif  // BASE_CHROMEOS_LOGGING_H_