Create a histogram serialization mechanism in components/metrics

components/metrics/chromeos/crash_sample.h

+// Copyright 2014 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 COMPONENTS_METRICS_CHROMEOS_CRASH_SAMPLE_H_
+#define COMPONENTS_METRICS_CHROMEOS_CRASH_SAMPLE_H_
+
+#include <string>
+
+#include "base/compiler_specific.h"
+#include "base/memory/scoped_ptr.h"
+#include "components/metrics/chromeos/metric_sample.h"
+
+namespace metrics {
+
+// Represent a crash event described by a simple name.
+class CrashSample : public MetricSample {
+ public:
+  explicit CrashSample(const std::string& crashname);
+  virtual ~CrashSample();
+
+  // Produce a serialized version of the crash.
+  // Format: crash\0|name_|\0
+  virtual std::string ToString() const OVERRIDE;
+
+  // Return a CrashSample object representing the serialized crash if possible.
+  // If the deserialization fails, returns NULL.
+  static scoped_ptr<CrashSample> ReadCrash(const std::string& crash_serialized);

[Luigi Semenzato, 2014/05/08 17:19:37]

I didn't know that there are "crash samples" in UMA.

[bsimonnet, 2014/05/08 20:02:58]

There is a way to log a crash (user crash, kernel crash or unclean shutdown of
the system) that will be reporter as a stability metric (crash count). I could
not find it on uma's metrics so I am not sure if we are still using it.

+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(CrashSample);
+};
+
+}  // namespace metrics
+
+#endif  // COMPONENTS_METRICS_CHROMEOS_CRASH_SAMPLE_H_