Kini Kini Transfer & Tours | Caribya!
Specializing in private ground transportation services and personalizes tours of the island, Kini Kini Transfer and Tours has been in operation since 2004 and has had many satisfied customers over the years.
If you hire Kini Kini for a private transfer, their uniformed representative will pick you up with a personalized sign so that you know exactly who will be driving you to your destination. They also offer a number of tours for guests to choose from.
The ATV Tour is an off-road adventure that encourages guests to explore the north coast with stops at Alto Vita Chapel, Baby Natural Bridge, Wish Garden, Bushiribana Ruins, Avo Rock Formations, and Natural Pool.
Aruba's Finest Island Tour is hosted by a knowledgeable guide on an air conditioned bus and takes guests to the Butterfly Farm, California Lighthouse, Alto Vista Chapel, Bushiribana Gold Melting Ruins, Natural Bridge, and Ostrich Farm.
The Country Side Tour is also given aboard an air conditioned bus and includes stops at the California Lighthouse, ALto Vista Chapel, Natural Bridge, Bushiriabana Ruins, Casibari Rock Formation, and Aloe Factory.
The Jeep Discovery Tour is a visit to the "wild" side of the island. Guests are welcome to drive themselves or enjoy the tour as a passenger as they visit the California Lighthouse, Wish Garden, Alto Vista Chapel, Bushirbana Gold Melting Ruin, Baby Natural Bridge, Ostrich Farm, and Ayo Rock Formation on the half day tour, or continue on for a full day to Black Stone Beach, Natural Pool, Sand Dunes, Fontein Caves, and Baby Beach.
The Beach and Snorkeling Adventure provides guests with a tour of some of the island's best south and west coast beaches including Baby Beach, Mangel Halto Beach, Boca Catalina Beach, and Malmok Beach.
Kini Kini's ATV tour is $110 for a single rider of $130(USD) for a double rider and includes bottled water and park entrance. If you'd prefer your tour be private, the rate goes up to $195 for a single rider and $230(USD) for a double rider.
Aruba's Finest Island Tour is $65 for adults and $35(USD) for children and includes entrance to the Butterfly Farm. Private tours are $115 for adults and $58(USD) for children.
The price for the Country Side Tour is $40 for adults and $20(US) for children.
If you're interested in a half day Jeep Discovery Tour, the cost is $90 for adults and $45(USD) for children, but $160 for adults and $80(USD) for children for a full day tour. Included in this option is bottled water, a barbecue lunch, farm entrance and park entrance. The cost of the private tour is $210 for adults and $105(USD) for children and it is only available as a half day adventure.
The half day snorkeling and beach tour is $50 for adults and $25(USD) for children, while the full day experience is $80 for adults and $40(USD) for children. Private tours are $75 for adults and $35(USD) for children and are only available for the half day tour. All tours include bottled water, snorkeling gear, and lunch.
The half day ATV Tour is from 9:00 a.m. to 1:00 p.m. and 2:00 to 6:00 p.m, as is the Aruba's Finest Island Tour. The Country Side Tour is available from 9:00 a.m. to noon and from 2:00 to 5:00 p.m. The Jeep Tour is from 9:00 a.m. to 1:00 p.m.
For all tours, children under the age of 12 must be accompanied by an adult, and for the ATV tours, children under the age of eight are not recommended.
Kini Kini Transfer & Tours is located in Oranjestad, north of downtown Oranjestad.


Nancy Carter tells us about her work alongside Bebe Moore Campbell spearheading NAMI Urban Los Angeles to reach communities of color, the origins of National Minority Mental Health Awareness Month, and her personal mental health journey going from family member to accomplished advocate to the sudden but enlightening perspective of newly diagnosed peer.
In honor of Bebe Moore Campbell National Minority Mental Health Awareness Month, we will be featuring filmed personal stories of recovery and hope by fellow community members across the state for our Bebe Moore Campbell video series. We will also feature events being put together by our affiliates in honor of this month. Join us by following and sharing our blog to bring awareness to the mental health needs and stories of underrepresented communities.


For Love, Balance, Breathing and the Sea Energy. Please choose your stone from the drop down menu.
Mermaids are so intimately linked with water that they both have become symbols of intuition, emotion, our subconscious and deeply primitive realms of mental perception. Syrians and Philistines worshiped a mermaid moon-goddess. The Syrians called her Atargatis while the Philistines knew her as Derceto. A symbol of eloquence and an emblem of enlightenment the mermaid also represented a safe voyage. Mermaids are also associated with love as they are frequently mentioned with love goddesses like Aphrodite/Venus. They are also affiliated with sea goddesses like Amphitrites, Tethys, Calypso and the Norse sea goddess, Rán.
Dolphins relish water both physically and mentally, swimming freely and going along with their natural feelings. They have a wise, innocent, purity of being which reaches out to our inner nature and beckons us to follow their lead and to open up to the energy of love, harmony and balance. Dolphin reminds us to get out, play and most importantly, to breathe.
The Mermaid/Dolphin Wand is a beautiful reminder of the elements and the necessity to maintain their balance within life – life of an individual and life of a people.
The textured shaft has a small sphere at the bottom and another sphere at the top.
Wand measures 8 inches long.
Made of fine 100% lead-free pewter for beauty, conductivity and quality.
Each wand is hand crafted here in the U.S. at Willowroot's Wand Studio.


text:
Pawpaw: In Search of America's Forgotten Fruit
Brand: Chelsea Green Publishing
Authors: by Andrew Moore (Author), Michael W. Twitty (Foreword)
Publisher : Chelsea Green Publishing; 1st edition (August 22, 2015)
The largest edible fruit native to the United States tastes like a cross between a banana and a mango. It grows wild in twenty-six states, gracing Eastern forests each fall with sweet-smelling, tropical-flavored abundance. Historically, it fed and sustained Native Americans and European explorers, presidents, and enslaved African Americans, inspiring folk songs, poetry, and scores of place names from Georgia to Illinois. Its trees are an organic grower's dream, requiring no pesticides or herbicides to thrive, and containing compounds that are among the most potent anticancer agents yet discovered.
So why have so few people heard of the pawpaw, much less tasted one?
In Pawpaw―a 2016 James Beard Foundation Award nominee in the Writing & Literature category―author Andrew Moore explores the past, present, and future of this unique fruit, traveling from the Ozarks to Monticello; canoeing the lower Mississippi in search of wild fruit; drinking pawpaw beer in Durham, North Carolina; tracking down lost cultivars in Appalachian hollers; and helping out during harvest season in a Maryland orchard. Along the way, he gathers pawpaw lore and knowledge not only from the plant breeders and horticulturists working to bring pawpaws into the mainstream (including Neal Peterson, known in pawpaw circles as the fruit's own "Johnny Pawpawseed"), but also regular folks who remember eating them in the woods as kids, but haven't had one in over fifty years.
As much as Pawpaw is a compendium of pawpaw knowledge, it also plumbs deeper questions about American foodways―how economic, biologic, and cultural forces combine, leading us to eat what we eat, and sometimes to ignore the incredible, delicious food growing all around us. If you haven't yet eaten a pawpaw, this book won't let you rest until you do.
"I'm always eager to read a talented writer's first book. For one thing, it's full of the infectious passion for the subject that usually drives someone to write it in the first place. But more than that, authors devote to such books the kind of attention usually reserved for a firstborn child―they are scrutinized and fretted over to the finest detail. Pawpaw, a heartfelt paean to a native North American tree with edible fruits, is just such a book. I have been growing pawpaws since 1970, but never realized how much I didn't know about the tree until reading Andrew Moore's book. A skilled storyteller, Moore delves deeply into the world of pawpaws while managing to hold the reader's interest through detail after detail. History, folklore, biology, taxonomy, hybridization, and everything else from slave sustenance to biochemical research are blended here."--Guy Sternberg, The American Gardener
Booklist-
"The pawpaw, also sometimes called the poor man's banana, is a common fruit growing in temperate zones across the U.S., yet it is rarely seen in the produce aisles. Hoping to shed more light on this culinary mystery, as well as inspire consumers and growers to make the fruit popular again, first-time author and gardener Moore offers both an engaging history and a thorough cultivation guide to the pawpaw. According to Moore, the shrub-like, large-leafed pawpaw tree typically grows in clumps near river bottoms along a belt running from northern Missouri to southern Louisiana and east as far as the Atlantic Ocean. Although historically pawpaw was eaten by Native Americans and slaves, it probably owes its marketplace anonymity to a short shelf life and widely variable flavors. While it remains to be seen whether Moore's well-written paean to the pawpaw will inspire increased production and distribution to grocery stores, uninitiated readers will be intrigued enough to want to sample the fruit at the first opportunity."
"Here is proof that culinary odysseys don't always need to involve globetrotting or the pursuit of rare, exotic foodstuffs. But, then again, in his pursuit of the lowly American pawpaw, Andrew Moore reminds us that America was once considered an exotic destiny on its own, and has always had more than its fair share of culinary rarities."--Damon Lee Fowler, author of Essentials of Southern Cooking and Beans, Greens, & Sweet Georgia Peaches
"Tropical growers have many shade crops to choose from, like cacao and coffee. Here in eastern North America we have our own luscious fruit for shady places―the pawpaw. Andrew Moore's Pawpaw tells the story of this fruit and the people working to bring it to our gardens, markets, and restaurants. It's the story of an eastern native fruit on its way to domestication, finally earning the place in our hearts and our cuisine that it deserves."--Eric Toensmeier, author of Paradise Lot and Perennial Vegetables
"Andrew Moore has done an amazing job demystifying one of America's most misunderstood and neglected fruits. Pawpaw deftly navigates between his own personal journey and the facts and history of the fruit, leaving readers―including chefs interested in heritage and tradition―with a true sense of how important it is to embrace this indigenous treasure."--Travis Milton, chef and co-owner of Shovel and Pick, Richmond, Virginia
"This book took me on an enchanting and engaging ride through the history, folklore, and science of a neglected but magical food plant. Andrew Moore shows us, in delightful prose and a wealth of fascinating stories, the role that the under-appreciated pawpaw has played in North American culture. I was constantly surprised to learn of the quiet influence the pawpaw has had on the people and environment around it, and like the author, am hopeful that it can find its rightful place among the better-known fruits that we all love."--Toby Hemenway, author of Gaia's Garden and The Permaculture City
"Like a gumshoe detective, Andrew Moore tracks down a mystery at once horticultural and culinary: Why is the pawpaw, America's largest indigenous fruit, so little known? The answer, like the fruit's beguiling taste, proves multi-layered and slippery, and after reading Moore's engaging account, I'm ready to light out for pawpaw country myself in search of this homegrown original."--Langdon Cook, author of The Mushroom Hunters: On the Trail of an Underground America
"This book is a love song, singing the praises of a unique, delicious, and once-abundant fruit that has been sadly neglected. Andrew Moore takes us on a very personal journey investigating how and why North America's largest indigenous fruit largely disappeared, and documenting efforts to revive it. Pawpaw is a pleasure to read, and if you do you'll probably find yourself searching for and loving these delectable fruits."--Sandor Ellix Katz, author of The Art of Fermentation
"America, get ready for pawpaw mania! Andrew Moore's book tells the definitive story of the wild fruit that is part of our nation's heritage, and in the process the author joins the ranks of food-preservationist heroes. Prepare to be overwhelmed with longing for the sweet scent and taste of the pawpaw."--Poppy Tooker, host of Louisiana Eats!
"Pawpaw: In Search of America's Forgotten Fruit is a fun and well-researched, informative romp through the culture and horticulture of this uncommon fruit. Uncommon, yes, but who would have imagined that there were and are quite a few other pawpaw nuts out there? If you don't know pawpaws, you should, and you will."--Lee Reich, PhD, author of Uncommon Fruits for Every Garden
Andrew Moore grew up in Lake Wales, Florida, just south of the pawpaw's native range. A writer and gardener, he now lives in Pittsburgh, Pennsylvania. He was the news editor and a feature writer for Pop City, a weekly news e-magazine in Pittsburgh, and his stories have been published in the Pittsburgh Post-Gazette, The Daily Yonder, and the Biscayne Times. Pawpaw is his first book.
Swim Through the Darkness: My Search for Craig Smith and the Mystery of Maitreya Kali

redpajama_set_name: RedPajamaCommonCrawl


As I promised at the start of the year I've tried to be brave and step out from behind the camera and show some of the sewing I have done for myself. First up is the Celestial Dress pattern from Pattern Fantastique.
This was such an impulse buy! I saw it for sale one day on Kollabora and took a risk. I'm so glad I did. It is a very quick sew with no buttons, zips or elastic. It comes in four different lengths; maxi, midi, mini and micro mini/tunic. Be warned though the maxi length will only fit on wide width fabrics! The instructions are very straightforward and there is a lovely top-stitching feature on the pockets and neckline. I think I'd love to make a plain version with some contrast stitching to highlight this feature.
This dress is unlike anything I have ever bought or made or wore for myself ever! It has very distinctive sleeves which are folded over so no sleeve hems :) It has a quite pronounced a-line shape but there are no darts or shaping. Most of the dresses I have made have been more typical fit and flare style so I was a little worried this may look like a bit of a tent on me.
The first I made was out of this bold sateen print from Spotlight. I think this dress pattern really suits a nice bold fabric and this seemed the best on the shelf. I knew I wanted to make a maxi version first so my choice were limited on the width.
I think it turned out nicely. The hem dips slightly in the back but the length is perfect for me. I was pretty pleased with the print matching I did on the yoke too, although I focused there so much I completely forgot to match the side seams!
After making the first dress and loving it I decided to try a midi version. I'd bought three metres of this fabric when it was on sale on a bit of a whim and it has worked nicely. This is a standard quilting cotton and I managed to cut the dress out comfortably. I made the size down in the one as I felt the maxi was a little gapey round the shoulders and back, although still wearable.
I think I like this length even better than the maxi. It works well with sandals or wedges but I think it will be fine in winter with some boots.
PS The PDF print out is a bit different from your typical pattern. The pieces are mostly inside the skirt portion. This didn't bother me too much as I always trace my patterns on to freezer paper and then cut them out. I didn't trace the skirt however. I cut out the front then trimmed the pattern piece to cut out the back. For my next one I will need to print it out again, but it really doesn't take up many sheets of paper.
What a great dress, thanks for the inspiration!
How nice. I have the pattern and can't wait to make it.


After freezing, stays cold for up to 3 hours. If dropped, the item will not shatter or break. After microwaving 30 seconds, the item will stay warm for 90 minutes. Condensation may potentially cause bubbling until cool.


text:
<!--
Copyright 2020 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.
-->

<!--
This file is used to generate a comprehensive list of Chrome OS histograms along
with a detailed description for each histogram.

For best practices on writing histogram descriptions, see
https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md

Prefer owners from the OWNERS file in this directory. If you need a metrics
reviewer, please send CLs to chromium-metrics-reviews@google.com rather than to
specific individuals. These CLs will be automatically reassigned to a reviewer
within about 5 minutes. This approach helps the metrics team to load-balance
incoming reviews. Googlers can read more about this at go/gwsq-gerrit.
-->

<histogram-configuration>

<histograms>

<variants name="FeaturesLoggingUsageEvents">
<!-- The variants are names of Chrome OS features. These are used for the
  ChromeOS.FeatureUsage.* histograms to record different events related to the
  feature -->

  <variant name="ClamshellLauncher" summary="app launcher in clamshell mode">
    <owner>jamescook@chromium.org</owner>
    <owner>tbarzic@chromium.org</owner>
    <owner>chromeos-launcher@google.com</owner>
  </variant>
  <variant name="DiagnosticsUi" summary="CROS Diagnostics Application">
    <owner>jimmyxgong@chromium.org</owner>
    <owner>zentaro@chromium.org</owner>
    <owner>cros-peripherals@google.com</owner>
  </variant>
  <variant name="ESim" summary="esim">
    <owner>azeemarshad@chromium.org</owner>
    <owner>cros-connectivity@google.com</owner>
    <owner>hsuregan@chromium.org</owner>
  </variant>
  <variant name="FastPair" summary="Fast Pair">
    <owner>shanefitz@google.com</owner>
    <owner>julietlevesque@google.com</owner>
    <owner>chromeos-cross-device-eng@google.com</owner>
  </variant>
  <variant name="Fingerprint" summary="fingerprint">
    <owner>rsorokin@chromium.org</owner>
    <owner>tomhughes@chromium.org</owner>
    <owner>cros-oac@google.com</owner>
    <owner>chromeos-fingerprint@google.com</owner>
  </variant>
  <variant name="LockOnSuspend" summary="lock screen on device suspend">
    <owner>rsorokin@chromium.org</owner>
    <owner>cros-oac@google.com</owner>
  </variant>
  <variant name="NearbyShare" summary="Nearby Share">
    <owner>nohle@chromium.org</owner>
    <owner>nearby-share-chromeos-eng@google.com</owner>
  </variant>
  <variant name="NearbyShareBackgroundScanning"
      summary="Background scanning for Nearby Share to detect and notify the
               user of devices nearby that are attempting to share">
    <owner>hansenmichael@google.com</owner>
    <owner>nearby-share-chromeos-eng@google.com</owner>
  </variant>
  <variant name="NumberpadDynamicActivations"
      summary="Turning on number pad mode for a dynamic numberpad.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadDynamicCancellations"
      summary="Turning off number pad mode for a dynamic numberpad, without
               having used a number-pad key.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadDynamicEnterKeystrokes"
      summary="Pressing enter on dynamic number pad.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadDynamicNonEnterKeystrokes"
      summary="Pressing key other than enter on dynamic number pad.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadExternalEnterKeystrokes"
      summary="Pressing number pad enter on external keyboard.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadExternalNonEnterKeystrokes"
      summary="Pressing number pad key other than enter on external keyboard.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadInternalEnterKeystrokes"
      summary="Pressing enter on number pad on internal keyboard.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="NumberpadInternalNonEnterKeystrokes"
      summary="Pressing number pad key other than enter on internal keyboard.">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="SmartLock" summary="Smart Lock">
    <owner>hansberry@chromium.org</owner>
    <owner>chromeos-cross-device-eng@google.com</owner>
  </variant>
  <variant name="StylusDetachedFromDockSession"
      summary="Time spent from stylus being undocked, to being re-docked">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="StylusDetachedFromGarageOrDockSession"
      summary="Time spent while either out of garage or un-docked">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="StylusDetachedFromGarageSession"
      summary="Time spent from stylus being removed from garage, to being
               replaced into garage">
    <owner>kenalba@google.com</owner>
    <owner>chromeos-tango@google.com</owner>
  </variant>
  <variant name="TabletLauncher" summary="app launcher in tablet mode">
    <owner>jamescook@chromium.org</owner>
    <owner>tbarzic@chromium.org</owner>
    <owner>chromeos-launcher@google.com</owner>
  </variant>
</variants>

<histogram name="ChromeOS.Apps.ExternalProtocolDialog"
    enum="ArcIntentHandlerAction" expires_after="2022-05-21">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <owner>mxcai@chromium.org</owner>
  <summary>
    Records the response when the intent picker is shown to the user on Chrome
    OS to allow them to open an external protocol in an app.
  </summary>
</histogram>

<histogram name="ChromeOS.Apps.ExternalProtocolDialog.Accepted"
    enum="ArcExternalProtocolAction" expires_after="2022-05-21">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <owner>mxcai@chromium.org</owner>
  <summary>
    Records the response when users that are shown the intent picker accept
    opening an external protocol in an app as well as whether the app is
    persisted.
  </summary>
</histogram>

<histogram name="ChromeOS.Apps.ExternalProtocolDialog.Rejected"
    enum="ArcExternalProtocolAction" expires_after="2022-05-21">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <owner>mxcai@chromium.org</owner>
  <summary>
    Records the response when users that are shown the intent picker reject
    opening an external protocol in an app.
  </summary>
</histogram>

<histogram name="ChromeOS.Apps.IntentPickerDestinationPlatform"
    enum="ArcIntentHandlerDestinationPlatform" expires_after="2022-05-21">
  <owner>elijahtaylor@google.com</owner>
  <owner>dominickn@chromium.org</owner>
  <owner>shihuis@google.com</owner>
  <summary>
    Records the app platform shown as the result of link intent handling.
    Recorded when the user makes a choice in the Intent Picker dialog, and when
    the result of a previous user preference is applied during a link click.
  </summary>
</histogram>

<histogram name="ChromeOS.Apps.NumberOfAppsForNotification"
    enum="BooleanMultipleApps" expires_after="2022-07-01">
  <owner>dominickn@chromium.org</owner>
  <owner>nancylingwang@chromium.org</owner>
  <summary>
    Records whether a notification matches multiple apps, when there is one or
    multiple web apps matching a web page nonpersistent notification.
  </summary>
</histogram>

<histogram name="ChromeOS.Apps.OpenBrowser" enum="OpenBrowserType"
    expires_after="2022-05-21">
  <owner>ajlinker@chromium.org</owner>
  <owner>dominickn@chromium.org</owner>
  <owner>mxcai@chromium.org</owner>
  <summary>
    Records the type of app sending a link to the browser to be opened.
  </summary>
</histogram>

<histogram name="ChromeOS.Attestation.AttestationFlowStatus"
    enum="AttestationFlowStatus" expires_after="2021-07-31">
  <owner>cylai@chromium.org</owner>
  <owner>cros-hwsec+umas@chromium.org</owner>
  <summary>
    Records the status of attestation flow. The value represents 6 flags in 6
    rightmost bits; starting from more significant bits they mean: 1. Has proxy.
    2. Is System proxy active. 3. Run the default flow. 4. The default flow
    succeeds. 5. Run the fallback flow. 6. The fallback flow succeeds.
  </summary>
</histogram>

<histogram name="ChromeOS.Attestation.GetCertificateStatus"
    enum="AttestationStatus" expires_after="2021-07-31">
  <owner>cylai@chromium.org</owner>
  <owner>cros-hwsec+umas@chromium.org</owner>
  <summary>
    Records the status of `AttesttionClient::GetCertificate()` called by
    `AttestationFlowIntegrated`.
  </summary>
</histogram>

<histogram base="true"
    name="ChromeOS.Camera.ConfigureStreams.Output.Resolution" units="pixels"
    expires_after="2022-10-01">
<!-- Name completed by histogram_suffixes
     name="ChromeOS.Camera.StreamFormat" -->

  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the resolution of output stream that is configured by Chrome OS
    camera service.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.ConfigureStreamsLatency" units="microseconds"
    expires_after="2022-10-01">
  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the process time of ConfigureStreams() method in Chrome OS camera
    service.

    This metric is reported for all users and will not cause abnormal
    distribution since the metric is Chrome OS specified.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.ErrorType" enum="ChromeOSCameraErrorType"
    expires_after="2022-10-01">
  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the type of the error which triggers the Notify() method in Chrome
    OS camera service.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.FaceAutoExposure.FunctionStatus"
    enum="ChromeOSCameraFaceAutoExposureFunctionStatus"
    expires_after="2022-11-16">
  <owner>mojahsu@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records face auto exposure function status of the Chrome OS device. The
    metric is reported when the camera is detected.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.FaceAutoExposure.MaxNumDetectedFaces"
    units="faces" expires_after="2022-11-16">
  <owner>mojahsu@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records max number of detected faces of the camera session in Chrome OS
    camera service. The metric is reported when the camera is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.Facing" enum="ChromeOSCameraFacing"
    expires_after="2022-10-01">
  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the camera facing of the camera session in Chrome OS camera service.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.GcamAutoExposure.AverageConvergenceLatency"
    units="frames" expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the average auto exposure convergence latency in frame count
    throughout a camera session that runs Gcam auto exposure. Emitted when the
    camera session is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.GcamAutoExposure.AverageHdrRatio"
    units="ratio" expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the average HDR ratio throughout a camera session that runs Gcam
    auto exposure. Emitted when the camera session is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.GcamAutoExposure.AverageTet" units="TET"
    expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the average total exposure time (TET) throughout a camera session
    that runs Gcam auto exposure. Emitted when the camera session is closed.
  </summary>
</histogram>

<histogram base="true"
    name="ChromeOS.Camera.HDRnet.AverageLatency.{ProcessingType}"
    units="microseconds" expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the average CPU latency in running a given type of processing
    throughout a HDRnet camera session. Emitted when the camera session is
    closed.

    This metric is reported on all ChromeOS devices with HDRnet enabled.
  </summary>
  <token key="ProcessingType">
    <variant name="Postprocessing"
        summary="Post-processing of HDRnet RGB output to final YUV output(s)"/>
    <variant name="Preprocessing"
        summary="Pre-processing of input YUV into linear RGB domain"/>
    <variant name="RgbPipeline"
        summary="Main HDRnet inferencing and rendering"/>
  </token>
</histogram>

<histogram name="ChromeOS.Camera.HDRnet.Error" enum="HdrnetError"
    expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records whether there's an error that can compromise the HDRnet feature,
    either causing frame drops or stops the pipeline from running completely,
    throughout a HDRnet camera session. Emitted when the camera session is
    closed.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.HDRnet.MaxOutputBuffersRendered"
    units="buffers" expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the maximum number of output buffers a HDRnet stream produces
    (greater than 1 means there are multiple streams with the same aspect ratio)
    throughtout a HDRnet camera session. Emitted when the camera session is
    closed.
  </summary>
</histogram>

<histogram base="true" name="ChromeOS.Camera.HDRnet.MaxStreamSize.{StreamType}"
    units="pixels" expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the maximum size (in width * height pixels) of the HDRnet stream
    configured for a given output in a HDRnet camera session. Emitted when the
    camera session is closed.
  </summary>
  <token key="StreamType">
    <variant name="BLOB" summary="HDRnet stream for BLOB output"/>
    <variant name="YUV" summary="HDRnet stream for YUV output"/>
  </token>
</histogram>

<histogram name="ChromeOS.Camera.HDRnet.NumConcurrentStreams" units="streams"
    expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the number of concurrent HDRnet streams in a HDRnet camera session.
    Emitted when the camera session is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.HDRnet.NumStillShotsTaken" units="captures"
    expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the number of HDRnet-rendered still capture shots taken in a HDRnet
    camera session. Emitted when the camera session is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.HDRnet.StreamConfiguration"
    enum="HdrnetStreamConfiguration" expires_after="2022-11-01">
  <owner>jcliang@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the stream configuration including the number of streams, the type
    of streams, and if the streams are of the same aspect ratio in a HDRnet
    camera session. Emitted when the camera session is closed.
  </summary>
</histogram>

<histogram base="true" name="ChromeOS.Camera.Jpeg.Latency" units="microseconds"
    expires_after="2022-10-01">
<!-- Name completed by histogram_suffixes
     name="ChromeOS.Camera.JpegProcessMethod" and
     name="ChromeOS.Camera.JpegProcessType" -->

  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the process time of the JDA (Jpeg Decode Accelerator) or JEA (Jpeg
    Encode Accelerator) run on Chrome OS camera service. There are suffixes that
    record the runner method (hardware/software), the runner type
    (decode/encode).

    This metric is reported for all users and will not cause abnormal
    distribution since the metric is Chrome OS specified.
  </summary>
</histogram>

<histogram base="true" name="ChromeOS.Camera.Jpeg.Resolution" units="pixels"
    expires_after="2022-10-01">
<!-- Name completed by histogram_suffixes
     name="ChromeOS.Camera.JpegProcessMethod" and
     name="ChromeOS.Camera.JpegProcessType" -->

  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the resolution of the image that JDA/JEA process by Chrome OS camera
    service. The resolution represents by the total pixels contained in the
    image. There are suffixes that record the runner method (hardware/software),
    the runner type (decode/encode).
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.OpenDeviceClientType"
    enum="ChromeOSCameraClientType" expires_after="2022-10-01">
  <owner>lnishan@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records which client type (e.g., Chrome, Android) is opening a camera
    device.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.OpenDeviceLatency" units="microseconds"
    expires_after="2022-10-01">
  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>
    Records the process time of OpenDevice() method in Chrome OS camera service.

    This metric is reported for all users and will not cause abnormal
    distribution since the metric is Chrome OS specified.
  </summary>
</histogram>

<histogram name="ChromeOS.Camera.SessionDuration" units="seconds"
    expires_after="2022-10-01">
  <owner>wtlee@chromium.org</owner>
  <owner>chromeos-camera-eng@google.com</owner>
  <summary>Records the session duration in Chrome OS camera service.</summary>
</histogram>

<histogram name="ChromeOS.CertProvisioning.CsrSignTime" units="ms"
    expires_after="2023-02-01">
  <owner>miersh@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    The amount of time it took the certificate provisioning worker to sign a
    CSR. Emitted after the sign is complete.
  </summary>
</histogram>

<histogram name="ChromeOS.CertProvisioning.Event" enum="CertProvisioningEvent"
    expires_after="2023-02-01">
  <owner>miersh@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    Number of times each event is reached during the certificate provisioning
    flow.
  </summary>
</histogram>

<histogram name="ChromeOS.CertProvisioning.KeypairGenerationTime" units="ms"
    expires_after="2023-02-01">
  <owner>miersh@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    The amount of time it took the certificate provisioning worker to generate
    one key pair. Emitted after the generation is complete.
  </summary>
</histogram>

<histogram name="ChromeOS.CertProvisioning.Result"
    enum="CertProvisioningWorkerState" expires_after="2023-02-01">
  <owner>miersh@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    For final states (see the list in cert_provisioning::IsFinalState): number
    of times the certificate provisioning worker finished on every state. For
    other states: number of times the worker failed on every state.
  </summary>
</histogram>

<histogram name="ChromeOS.CertProvisioning.VaTime" units="ms"
    expires_after="2023-02-01">
  <owner>miersh@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    The amount of time it took the certificate provisioning worker to build one
    Verified Access response. Emitted after the response is built.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.CollectPerf"
    enum="ChromeOSProfileCollectionStatus" expires_after="2022-05-01">
  <owner>aalexand@google.com</owner>
  <owner>gmx@chromium.org</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    A count of successes and various failure modes related to collecting and
    processing profile data obtained via "perf events" on Chrome OS.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.CollectProcessTypes"
    enum="ChromeOSProcessTypeCollectionStatus" expires_after="2023-01-19">
  <owner>aalexand@google.com</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    Record the collection status (success or failure) when the Chrome process
    and thread types are collected as part of the ChromeOS perf profile
    collection.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.JankinessTriggerStatus"
    enum="ChromeOSJankinessTriggerStatus" expires_after="2023-03-30">
  <owner>chinglinyu@chromium.org</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    Records the status of collection attempts triggered by jankiness on Chrome
    OS.

    Warning: this histogram was expired from 08/30/2020 to 03/30/2022; data may
    be missing.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.ParseCPUFrequencies"
    enum="ChromeOSParseCPUFrequencyStatus" expires_after="2022-05-01">
  <owner>gmx@chromium.org</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    A count of successes and various failure modes related to the parsing of
    logical CPU frequencies on Chrome OS. Recorded when the browser process
    starts.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.ParsePSICPU" enum="ChromeOSParsePSICPUStatus"
    expires_after="2022-05-01">
  <owner>shantuo@google.com</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    A count of successes and various failure modes related to the parsing of PSI
    CPU data on Chrome OS. Recorded after each perf collection.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.ParsePSIMemory" enum="ChromeOSParsePSIMemStatus"
    expires_after="2022-06-01">
  <owner>raging@google.com</owner>
  <owner>chromeos-memory@google.com</owner>
  <summary>
    A count of successes and various failure modes related to the parsing of PSI
    Memory data on Chrome OS. Recorded after each perf collection.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.PSIMemPressure.{PType}" units="failures"
    expires_after="2022-12-01">
  <owner>raging@google.com</owner>
  <owner>chromeos-memory@google.com</owner>
  <summary>
    Reports periodic memory pressure metrics, as seen ChromeOS-wide. Metrics
    originally come from /proc/pressure/memory readings, expressed as a
    percentage with 2 decimal points (99.99%), but expressed as p*100, in an
    integer in the range (1-9999) meaning (00.01% to 99.99%). Underflow value 0
    means "no pressure" - 0%.
  </summary>
  <token key="PType">
    <variant name="ArcFull"
        summary="Percentage of time ARC was fully halted waiting on memory"/>
    <variant name="ArcSome"
        summary="Percentage of ARC had some blocking on memory"/>
    <variant name="Full"
        summary="Percentage of time fully halted waiting on memory operations"/>
    <variant name="Some"
        summary="Percentage of time when there was some blocking on memory"/>
  </token>
</histogram>

<histogram name="ChromeOS.CWP.RecordPerf" enum="ChromeOSProfileRecordStatus"
    expires_after="2022-12-20">
  <owner>shantuo@google.com</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    A count of the various outcomes related to recording the profile data
    collected via "perf events" on Chrome OS. The histogram is
    recorded when system-wide CPU profiling finishes and the collected data is
    being saved to memory for later upload.
  </summary>
</histogram>

<histogram name="ChromeOS.CWP.UploadPerf" units="reports"
    expires_after="2023-03-30">
  <owner>aalexand@google.com</owner>
  <owner>gmx@chromium.org</owner>
  <owner>cwp-team@google.com</owner>
  <summary>
    Records the number of "perf events" reports included in an UMA
    upload on Chrome OS.
  </summary>
</histogram>

<histogram name="ChromeOS.Debugd.Perf.{FunctionName}" units="ms"
    expires_after="2023-01-01">
  <owner>enlightened@google.com</owner>
  <owner>jorgelo@google.com</owner>
  <owner>chromeos-security-core@google.com</owner>
  <summary>
    Records the total time it takes for each call to LogTool::{FunctionName} to
    complete. Recording happens on each D-Bus call to debugd.
  </summary>
  <token key="FunctionName">
    <variant name="GetAllDebugLogs"/>
    <variant name="GetAllLogs"/>
    <variant name="GetBigFeedbackLogs"/>
  </token>
</histogram>

<histogram name="ChromeOS.DeviceSettings.FeatureFlagsMigration"
    enum="DeviceSettingsFeatureFlagsMigrationStatus" expires_after="2022-04-10">
  <owner>mnissler@chromium.org</owner>
  <owner>src/chrome/browser/ash/settings/OWNERS</owner>
  <summary>
    Migration status for Chrome OS feature flags configuration in device
    settings. This is intended to track migration progress in the field, so the
    migration code can be removed when the old approach of storing bare flags is
    no longer relevant in the field.
  </summary>
</histogram>

<histogram name="ChromeOS.DiagnosticsUi.InitialScreen"
    units="CrosDiagnosticsNavigationView" expires_after="2022-06-15">
  <owner>gavindodd@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records requested initial screen when opening the Diagnostics App.
  </summary>
</histogram>

<histogram name="ChromeOS.DiagnosticsUi.MemoryRoutineDuration" units="s"
    expires_after="2022-06-15">
  <owner>gavindodd@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records the duration that the Memory Routine took to complete. Emitted when
    the routine completes successfully.
  </summary>
</histogram>

<histogram name="ChromeOS.DiagnosticsUi.OpenDuration" units="ms"
    expires_after="2022-06-15">
  <owner>gavindodd@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records the duration that the Diagnostics App is open. emitted when the app
    is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.DiagnosticsUi.RoutineCount" units="routines"
    expires_after="2022-06-15">
  <owner>gavindodd@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records the number of routines run while the Chrome OS Diagnostics App was
    open. Begins at zero each time the app is open and recorded each time the
    app is closed.
  </summary>
</histogram>

<histogram name="ChromeOS.DiagnosticsUi.{RoutineType}Result"
    enum="CrosDiagnosticsRoutineResult" expires_after="2022-06-15">
  <owner>gavindodd@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>Records the result of the {RoutineType} Routine.</summary>
  <token key="RoutineType">
    <variant name="BatteryCharge"/>
    <variant name="BatteryDischarge"/>
    <variant name="CaptivePortal"/>
    <variant name="CpuCache"/>
    <variant name="CpuFloatingPoint"/>
    <variant name="CpuPrime"/>
    <variant name="CpuStress"/>
    <variant name="DnsLatency"/>
    <variant name="DnsResolution"/>
    <variant name="DnsResolverPresent"/>
    <variant name="GatewayCanBePinged"/>
    <variant name="HasSecureWiFiConnection"/>
    <variant name="HttpFirewall"/>
    <variant name="HttpsFirewall"/>
    <variant name="HttpsLatency"/>
    <variant name="LanConnectivity"/>
    <variant name="Memory"/>
    <variant name="SignalStrength"/>
  </token>
</histogram>

<histogram name="ChromeOS.FeatureUsage.{FeatureName}" enum="FeatureUsageEvent"
    expires_after="2022-11-11">
  <owner>rsorokin@chromium.org</owner>
  <owner>cros-oac@google.com</owner>
  <summary>
    Records device eligibility, enabled status, and success rate for the
    {FeatureName} feature. Different events are recorded at different times, as
    described in the enum labels.
  </summary>
  <token key="FeatureName" variants="FeaturesLoggingUsageEvents"/>
</histogram>

<histogram name="ChromeOS.FeatureUsage.{FeatureName}.Usetime" units="ms"
    expires_after="2022-11-11">
  <owner>rsorokin@chromium.org</owner>
  <owner>cros-oac@google.com</owner>
  <summary>
    Records the duration of time (ms) a given {FeatureName} feature was used.
  </summary>
  <token key="FeatureName" variants="FeaturesLoggingUsageEvents"/>
</histogram>

<histogram name="ChromeOS.FirmwareUpdateUi.InstallResult"
    enum="FirmwareUpdateInstallResult" expires_after="2023-01-01">
  <owner>jimmyxgong@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records the result of installing a firmware update. Recorded once per
    install and the histogram is emitted either when an install is completed or
    when a failure state is reached. An example failure state is if we're unable
    to create a firmware update directory.
  </summary>
</histogram>

<histogram name="ChromeOS.FirmwareUpdateUi.{Source}.DeviceCount"
    units="devices" expires_after="2023-01-01">
  <owner>jimmyxgong@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records the total number of devices found. OnStartup is recorded when a user
    first logs in and OnRefresh is recorded for any subsequent request. The
    cases in which a subsequent request will be made are when the Firmware
    Update SWA is launched, when an install is completed, and when we detect
    that a device has been added or removed.
  </summary>
  <token key="Source">
    <variant name="OnRefresh"/>
    <variant name="OnStartup"/>
  </token>
</histogram>

<histogram name="ChromeOS.FirmwareUpdateUi.{Source}.{Severity}UpdateCount"
    units="updates" expires_after="2023-01-01">
  <owner>jimmyxgong@chromium.org</owner>
  <owner>zentaro@chromium.org</owner>
  <owner>cros-peripherals@google.com</owner>
  <summary>
    Records the total number of {Severity} firmware updates found for all of the
    peripherals currently connected. The histogram is emitted once we've
    received the list of updates (if any) for all peripherals. OnStartup is
    recorded when a user first logs in and OnRefresh is recorded for any
    subsequent request. The cases in which a subsequent request will be made are
    when the Firmware Update SWA is launched, when an install is completed, and
    when we detect that a device has been added or removed.
  </summary>
  <token key="Source">
    <variant name="OnRefresh"/>
    <variant name="OnStartup"/>
  </token>
  <token key="Severity">
    <variant name="Critical"/>
  </token>
</histogram>

<histogram name="ChromeOS.Gaia.Message.{GaiaAuthFlow}.{MessageName}"
    enum="BooleanReceived" expires_after="2022-06-01">
  <owner>rsorokin@chromium.org</owner>
  <owner>cros-oac@google.com</owner>
  <summary>
    Records whether or not {MessageName} was received during the {GaiaAuthFlow}
    authentication on the login screen. Recorded on the successful online
    authentication only.
  </summary>
  <token key="GaiaAuthFlow">
    <variant name="Gaia"/>
    <variant name="Saml"/>
  </token>
  <token key="MessageName">
    <variant name="CloseView"/>
    <variant name="UserInfo"/>
  </token>
</histogram>

<histogram name="ChromeOS.Gaia.PasswordFlow" enum="BooleanStartedCompleted"
    expires_after="2022-06-01">
  <owner>rsorokin@chromium.org</owner>
  <owner>cros-oac@google.com</owner>
  <summary>
    Records events for the Gaia password flow. "Started" is recorded
    on each password entry on the Gaia page. "Completed" is recorded
    when Gaia authentication succeeds. Note: this is not recorded for SAML
    flows.
  </summary>
</histogram>

<histogram base="true" name="ChromeOS.HardwareVerifier.Report"
    enum="HardwareVerifierQualificationStatus" expires_after="2023-03-01">
<!-- Name completed by histogram_suffixes name="HardwareVerifierSupportCategory" -->

  <owner>itspeter@chromium.org</owner>
  <owner>stimim@chromium.org</owner>
  <owner>chromeos-runtime-probe@google.com</owner>
  <summary>
    Qualification status of each component types. This entry is generated by
    hardware_verifier.conf at boot time.
  </summary>
</histogram>

<histogram name="ChromeOS.HardwareVerifier.Report.IsCompliant" enum="Boolean"
    expires_after="2023-03-01">
  <owner>itspeter@chromium.org</owner>
  <owner>stimim@chromium.org</owner>
  <owner>chromeos-runtime-probe@google.com</owner>
  <summary>Aggregated result of hardware verifier check.</summary>
</histogram>

<histogram name="ChromeOS.HardwareVerifier.TimeToFinish" units="ms"
    expires_after="2023-03-01">
  <owner>itspeter@chromium.org</owner>
  <owner>stimim@chromium.org</owner>
  <owner>chromeos-runtime-probe@google.com</owner>
  <summary>
    The amount of time it takes to finish one hardware verification run.
  </summary>
</histogram>

<histogram name="ChromeOS.HardwareVerifier.TimeToProbe" units="ms"
    expires_after="2023-03-01">
  <owner>itspeter@chromium.org</owner>
  <owner>stimim@chromium.org</owner>
  <owner>chromeos-runtime-probe@google.com</owner>
  <summary>The amount of time it takes to probe hardware components.</summary>
</histogram>

<histogram name="ChromeOS.IioService.SensorClientConcurrent" units="clients"
    expires_after="2022-05-01">
  <owner>chenghaoyang@chromium.org</owner>
  <owner>chromeos-sensors-eng@google.com</owner>
  <summary>
    Records the maximum number of concurrent sensor clients within an hour,
    which indicates how many apps are using sensors. Recorded once every hour.
    Might not be recorded for tail-end usage during a session.
  </summary>
</histogram>

<histogram name="ChromeOS.IioService.SensorObserver" units="observers"
    expires_after="2022-05-01">
  <owner>chenghaoyang@chromium.org</owner>
  <owner>chromeos-sensors-eng@google.com</owner>
  <summary>
    Records the maximum number of running observers within an hour to any
    sensor. It indicates how widely used the sensor samples are. Recorded once
    every hour. Might not be recorded for tail-end usage during a session.
  </summary>
</histogram>

<histogram name="ChromeOS.IioService.SensorObserverOpen" units="observers"
    expires_after="2022-05-01">
  <owner>chenghaoyang@chromium.org</owner>
  <owner>chromeos-sensors-eng@google.com</owner>
  <summary>
    Records the number of opened observer within an hour, which indicates how
    often sensors are enabled and disabled. Recorded once every hour. Might not
    be recorded for tail-end usage during a session.
  </summary>
</histogram>

<histogram name="ChromeOS.IioService.SensorUsage.{Frequency}Hz"
    enum="ChromeOSIioServiceSensorUsage" expires_after="2022-05-01">
  <owner>chenghaoyang@chromium.org</owner>
  <owner>chromeos-sensors-eng@google.com</owner>
  <summary>
    Records the usage of the sensor within an hour with at least {Frequency} Hz.
    Recorded once every hour. Might not be recorded for tail-end usage during a
    session.
  </summary>
  <token key="Frequency">
    <variant name="0"/>
    <variant name="10"/>
    <variant name="50"/>
    <variant name="100"/>
  </token>
</histogram>

<histogram name="ChromeOS.Intents.IntentPickerAction"
    enum="IntentPickerDialogAction" expires_after="2022-06-01">
  <owner>tsergeant@chromium.org</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    The intent picker dialog is shown (either automatically, or though a page
    action button) when the user navigates to a page whose URL can be handled by
    an installed app. This metric is recorded when the dialog is closed and
    records the user action which caused it to close.
  </summary>
</histogram>

<histogram name="ChromeOS.Intents.IntentPickerAction.From{LaunchSource}"
    enum="IntentPickerDialogAction" expires_after="2022-06-01">
  <owner>tsergeant@chromium.org</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    The intent picker dialog is shown when the user navigates to a page whose
    URL can be handled by an installed app. This metric is recorded when the
    dialog is closed and records the user action which caused it to close. Only
    recorded when the Intent Picker dialog is shown from {LaunchSource}.
  </summary>
  <token key="LaunchSource">
    <variant name="AutoPopOut"/>
    <variant name="OmniboxIcon"/>
  </token>
</histogram>

<histogram name="ChromeOS.Intents.IntentPickerIconEvent"
    enum="IntentPickerIconEvent" expires_after="2022-06-01">
  <owner>tsergeant@chromium.org</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    Records events associated with the intent picker icon in the omnibox.
    Recorded when the icon is shown or interacted with.
  </summary>
</histogram>

<histogram name="ChromeOS.IsLacrosBrowser" enum="Boolean" expires_after="never">
<!-- expires-never: Used to identify lacros binary in metrics backend. -->

  <owner>jamescook@chromium.org</owner>
  <owner>lacros-team@google.com</owner>
  <summary>
    Recorded as part of the metrics session data to identify the lacros-chrome
    browser binary.
  </summary>
</histogram>

<histogram name="ChromeOS.KeyPermissionsManager.ArcUsageUpdate"
    enum="KeyPermissionsManagerArcUsageUpdateStatus" expires_after="2022-02-06">
  <owner>omorsi@google.com</owner>
  <owner>pmarko@google.com</owner>
  <summary>
    Counts the number of times the arc usage flags update started as well as the
    number of times it succeeded and failed.
  </summary>
</histogram>

<histogram name="ChromeOS.KeyPermissionsManager.ArcUsageUpdateTime" units="ms"
    expires_after="2022-02-06">
  <owner>omorsi@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    Records the time taken to successfully update chaps with the new ARC usage
    flags.
  </summary>
</histogram>

<histogram name="ChromeOS.KeyPermissionsManager.Migration"
    enum="KeyPermissionsManagerMigrationStatus" expires_after="2022-05-01">
  <owner>omorsi@google.com</owner>
  <owner>pmarko@google.com</owner>
  <summary>
    Counts the number of times the migration started as well as the number of
    times it succeeded and failed.
  </summary>
</histogram>

<histogram name="ChromeOS.KeyPermissionsManager.MigrationTime" units="ms"
    expires_after="2022-02-06">
  <owner>omorsi@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    Records the time taken to successfully migrate key permissions to chaps.
  </summary>
</histogram>

<histogram name="ChromeOS.Lacros.OSChannel" enum="ChromeOSChannel"
    expires_after="2022-10-01">
  <owner>erikchen@chromium.org</owner>
  <owner>lacros-team@google.com</owner>
  <summary>
    The release channel of the Chrome OS system on which Lacros is running. May
    be different than the Lacros browser release channel. Recorded by the lacros
    binary shortly after startup.
  </summary>
</histogram>

<histogram name="ChromeOS.Lacros.StartTime" units="ms"
    expires_after="2022-10-01">
  <owner>erikchen@chromium.org</owner>
  <owner>lacros-team@google.com</owner>
  <summary>
    Time to start the lacros binary, specifically the time between when the
    process is launched and the mojo connection is established between ash and
    lacros. Recorded by ash each time the lacros binary is started.
  </summary>
</histogram>

<histogram name="ChromeOS.LanguagePacks.InstallComplete.Success"
    enum="BooleanSuccess" expires_after="2022-10-01">
  <owner>claudiomagni@chromium.org</owner>
  <owner>mlcui@google.com</owner>
  <owner>dvallet@chromium.org</owner>
  <summary>
    Records whether a language pack installation was successful after a language
    pack installation attempt.
  </summary>
</histogram>

<histogram name="ChromeOS.LanguagePacks.Mojo.GetPackInfo.Feature"
    enum="LanguagePackMojoFeatureId" expires_after="2022-10-01">
  <owner>mlcui@google.com</owner>
  <owner>cros-borders-eng@google.com</owner>
  <summary>
    Records which feature was requested by callers of the language packs Mojo
    interface's "GetPackInfo" IPC call.
  </summary>
</histogram>

<histogram name="ChromeOS.LanguagePacks.Mojo.InstallPack.Feature"
    enum="LanguagePackMojoFeatureId" expires_after="2022-10-01">
  <owner>mlcui@google.com</owner>
  <owner>cros-borders-eng@google.com</owner>
  <summary>
    Records which feature was requested by callers of the language packs Mojo
    interface's "InstallPack" IPC call.
  </summary>
</histogram>

<histogram name="ChromeOS.LanguagePacks.Mojo.PackStateResponse"
    enum="LanguagePackMojoPackState" expires_after="2022-10-01">
  <owner>mlcui@google.com</owner>
  <owner>cros-borders-eng@google.com</owner>
  <summary>
    Records the state of what state a language pack is in (whether it's
    installed or not) when the language packs Mojo interface responds to an IPC.
  </summary>
</histogram>

<histogram name="ChromeOS.LanguagePacks.UninstallComplete.Success"
    enum="BooleanSuccess" expires_after="2022-10-01">
  <owner>claudiomagni@chromium.org</owner>
  <owner>mlcui@google.com</owner>
  <owner>dvallet@chromium.org</owner>
  <summary>
    Records whether a language pack uninstallation was successful after a
    language pack uninstallation attempt.
  </summary>
</histogram>

<histogram name="ChromeOS.Liveness.BrowserStateAtTimeout"
    enum="ChromeOSBrowserProcessState" expires_after="2023-01-30">
  <owner>iby@google.com</owner>
  <owner>xiyuan@google.com</owner>
  <owner>kaznacheev@google.com</owner>
  <summary>
    Records the state of the Chrome browser process at the moment
    session_manager's LivenessChecker ping times out. This is the moment when
    LivenessChecker will send an abort signal, if sending an abort signal is
    enabled, but this metric is recorded regardless of whether or not aborting
    from LivenessChecker is enabled. Exactly one sample of this metric is
    recorded when the timeout occurs. If aborting is enabled, this should mean
    one sample per abort.
  </summary>
</histogram>

<histogram name="ChromeOS.Liveness.PingResponseTime" units="ms"
    expires_after="2022-08-05">
  <owner>rtinkoff@google.com</owner>
  <owner>xiyuan@google.com</owner>
  <summary>
    Reports the time (ms) elapsed between sending of a LivenessChecker ping and
    receipt of the response. Recorded when LivenessChecker receives a ping
    response.
  </summary>
</histogram>

<histogram name="ChromeOS.Liveness.PingResult" enum="BooleanSuccess"
    expires_after="2023-02-04">
  <owner>iby@google.com</owner>
  <owner>xiyuan@google.com</owner>
  <summary>
    Records whether the dbus liveness pings successfully go through. True is
    recorded when the session manager daemon receives the pong back from chrome
    in time. False is recorded when it times out waiting for the pong.
  </summary>
</histogram>

<histogram name="ChromeOS.Logging.{LogType}EntryCountPerDay"
    units="log entries per day" expires_after="2021-07-31">
  <owner>yoshiki@chromium.org</owner>
  <owner>chromeos-velocity@chromium.org</owner>
  <summary>
    Metrics of the numbers of log entries recorded in {LogType}s. Recorded when
    the daily job "chromeos-cleanup-logs" is executed.
  </summary>
  <token key="LogType">
    <variant name="SystemLog"/>
    <variant name="UserLog"/>
  </token>
</histogram>

<histogram name="ChromeOS.Logging.{LogType}LogFileSizePerDay" units="MB"
    expires_after="2021-07-31">
  <owner>yoshiki@chromium.org</owner>
  <owner>chromeos-velocity@chromium.org</owner>
  <summary>
    File sizes of {LogType} files in megabytes. Recorded when the daily job
    "chromeos-cleanup-logs" is executed.
  </summary>
  <token key="LogType">
    <variant name="SystemArc"/>
    <variant name="SystemAudit"/>
    <variant name="SystemChrome"/>
    <variant name="SystemMessage"/>
    <variant name="SystemNet"/>
    <variant name="UserChrome"/>
  </token>
</histogram>

<histogram name="ChromeOS.Logging.{LogType}MaxThroughputPerMin"
    units="log entries per min" expires_after="2021-07-31">
  <owner>yoshiki@chromium.org</owner>
  <owner>chromeos-velocity@chromium.org</owner>
  <summary>
    Metrics of the number of maximum throughput (entries per minute) recorded in
    {LogType}s within a day. Recorded when the daily job
    "chromeos-cleanup-logs" is executed.
  </summary>
  <token key="LogType">
    <variant name="SystemLog"/>
    <variant name="UserLog"/>
  </token>
</histogram>

<histogram name="ChromeOS.Logging.{LogType}TotalFileSize" units="MB"
    expires_after="2021-07-31">
  <owner>yoshiki@chromium.org</owner>
  <owner>chromeos-velocity@chromium.org</owner>
  <summary>
    Total file sizes of {LogType} files in megabytes. Recorded when the daily
    job "chromeos-cleanup-logs" is executed.
  </summary>
  <token key="LogType">
    <variant name="SystemLog"/>
    <variant name="UserLog"/>
  </token>
</histogram>

<histogram name="ChromeOS.MachineIdRegen.AgeSeconds" units="seconds"
    expires_after="2022-02-02">
  <owner>ahassani@chromium.org</owner>
  <owner>chromeos-core-services@google.com</owner>
  <summary>
    The number of seconds of uptime since the last time the Chrome OS machine-id
    was regenerated. This is reported every time the machine-id is regenerated
    except for the first time since reboot.

    NB: Data before M90 is incomplete.
  </summary>
</histogram>

<histogram name="ChromeOS.MachineIdRegen.Lock" enum="BooleanLockingSuccess"
    expires_after="2022-02-02">
  <owner>ahassani@chromium.org</owner>
  <owner>chromeos-core-services@google.com</owner>
  <summary>
    Measures whether the MachineIdRegen script acquires the lock. Success / Fail
    is recorded every time the script is invoked. This is to test if the locking
    is working as expected.
  </summary>
</histogram>

<histogram name="ChromeOS.MachineIdRegen.Reason" enum="ChromeOSMachineIdReason"
    expires_after="2022-05-01">
  <owner>ahassani@chromium.org</owner>
  <owner>chromeos-core-services@google.com</owner>
  <summary>
    The reason why the Chrome OS machine-id was regenerated. This is reported
    when the machine-id is re-generated.

    NB: Data before M90 is incomplete.
  </summary>
</histogram>

<histogram name="ChromeOS.MemoryPressureLevel" enum="MemoryPressureLevel"
    expires_after="2022-04-24">
  <owner>xdai@chromium.org</owner>
  <summary>
    The memory pressure level in Chrome OS, which is recorded periodically (once
    per second). This is used to show the relative frequency of the system being
    in a critical vs relaxed memory pressure state.
  </summary>
</histogram>

<histogram name="ChromeOS.MessageCenter.ScrollActionReason"
    enum="ChromeOSMessageCenterScrollActionReason" expires_after="2022-11-22">
  <owner>yoshiki@chromium.org</owner>
  <owner>omrilio@chromium.org</owner>
  <owner>leandre@chromium.org</owner>
  <owner>cros-status-area-eng@google.com</owner>
  <summary>
    The cause of the scroll event by the user on the message center. Only the
    first event after the message center opens is recorded. For example, the
    user opens the message center and scrolls by mouse then by key, only the
    mouse event is recorded. If the user closes and reopens the message center
    before the second event, both events are recorded.
  </summary>
</histogram>

<histogram name="ChromeOS.PlatformKeysService.{Operation}.{KeyType}"
    enum="BooleanSuccess" expires_after="2022-03-19">
  <owner>omorsi@google.com</owner>
  <owner>mgawad@google.com</owner>
  <summary>
    Tracks the final result of performing {Operation} operation on an {KeyType}
    key in PlatformKeysService.
  </summary>
  <token key="Operation">
    <variant name="GenerateKey"/>
    <variant name="SignKey"/>
  </token>
  <token key="KeyType">
    <variant name="EC"/>
    <variant name="RSA"/>
  </token>
</histogram>

<histogram name="ChromeOS.PlatformVerification.Available"
    enum="BooleanAvailable" expires_after="2021-12-21">
  <owner>apronin@chromium.org</owner>
  <owner>cros-hwsec+uma@chromium.org</owner>
  <summary>
    Whether platform verification subsystem features are available at the time a
    platform verification request is made for content protection on Chrome OS.
  </summary>
</histogram>

<histogram name="ChromeOS.PlatformVerification.BrowserResult"
    enum="ChromeOSPlatformVerificationBrowserResult" expires_after="2022-05-21">
  <owner>erikchen@chromium.org</owner>
  <owner>cros-hwsec+uma@chromium.org</owner>
  <summary>
    The result of a platform verification attempt for content protection on
    Chrome OS, limited to the browser-specific checks. It's still possible for
    platform verification to fail at later layers.
  </summary>
</histogram>

<histogram name="ChromeOS.PlatformVerification.Result2"
    enum="ChromeOSPlatformVerificationResult2" expires_after="2022-09-11">
  <owner>erikchen@chromium.org</owner>
  <owner>cros-hwsec+uma@chromium.org</owner>
  <summary>
    The result of a platform verification attempt for content protection on
    Chrome OS. Does not include browser-related failures. Those are tracked in
    ChromeOS.PlatformVerification.BrowserResult.
  </summary>
</histogram>

<histogram name="ChromeOS.PrivacyScreen.Toggled"
    enum="PrivacyScreenToggleUISurface" expires_after="2022-04-01">
  <owner>tengs@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    Record when the user toggles the integrated privacy screen on/off. See the
    PrivacyScreenToggleUISurface enum for all UI surfaces for toggling the
    feature.
  </summary>
</histogram>

<histogram name="ChromeOS.SAML.APILogin" enum="ChromeOSSamlApiUsed"
    expires_after="2022-04-02">
  <owner>mslus@chromium.org</owner>
  <owner>emaxx@chromium.org</owner>
  <summary>
    Records every online login authenticated purely with GAIA or with SAML.
  </summary>
</histogram>

<histogram name="ChromeOS.SAML.InSessionPasswordChangeEvent"
    enum="SamlInSessionPasswordChangeEvent" expires_after="2022-03-12">
  <owner>mslus@chromium.org</owner>
  <owner>rsorokin@chromium.org</owner>
  <summary>
    Records how often users are guided through the SAML in-session password
    change flow, and how often it is completed succesfully.
  </summary>
</histogram>

<histogram name="ChromeOS.SAML.InSessionPasswordSyncEvent"
    enum="SamlInSessionPasswordSyncEvent" expires_after="2022-04-30">
  <owner>mslus@chromium.org</owner>
  <owner>mohammedabdon@chromium.org</owner>
  <summary>
    Records how often password sync token API is called. Tracks results of token
    verify operation and API errors.
  </summary>
</histogram>

<histogram name="ChromeOS.SAML.Provider" enum="ChromeOSSamlProvider"
    expires_after="2022-04-17">
  <owner>mslus@chromium.org</owner>
  <owner>mohammedabdon@chromium.org</owner>
  <summary>Records SAML provider when SAML login flow is used.</summary>
</histogram>

<histogram name="ChromeOS.SAML.SamlChallengeKeyHandlerResult"
    enum="SamlChallengeKeyHandlerResult" expires_after="2022-02-01">
  <owner>miersh@google.com</owner>
  <owner>pmarko@chromium.org</owner>
  <summary>
    Tracks results of calculating response for a challenge from Verified Access
    server for remove attestation during SAML authentication.
  </summary>
</histogram>

<histogram name="ChromeOS.SAML.Scraping.PasswordCountAll" units="passwords"
    expires_after="2022-03-21">
  <owner>mslus@chromium.org</owner>
  <owner>emaxx@chromium.org</owner>
  <summary>
    The number of passwords that were scraped during a Chrome OS login via SAML.
    This is set only when the Chrome Credentials Passing API is not used.
  </summary>
</histogram>

<histogram name="ChromeOS.SAML.Scraping.VerificationResult"
    enum="BooleanSuccess" expires_after="M78">
  <owner>bartfab@chromium.org</owner>
  <summary>
    Whether one of the scraped passwords was successfully verified as the user's
    password. This is set only when the Chrome Credentials Passing API is not
    used.
  </summary>
</histogram>

<histogram name="ChromeOS.SecurityAnomaly" enum="SecurityAnomaly"
    expires_after="2022-10-03">
  <owner>jorgelo@chromium.org</owner>
  <owner>chromeos-security-core@google.com</owner>
  <summary>
    Records when an event representing a deviation from the Chrome OS security
    posture happens.

    Writable+executable mount events are checked every thirty seconds, but each
    anomalous event is reported only once per boot.
  </summary>
</histogram>

<histogram name="ChromeOS.SecurityAnomalyUploadSuccess" enum="Boolean"
    expires_after="2022-10-03">
  <owner>jorgelo@chromium.org</owner>
  <owner>chromeos-security-core@google.com</owner>
  <summary>
    Records the result (boolean success or failure) of attempting to report a
    Chrome OS system as anomalous via the crash reporting service.

    Reporting is only attempted if one or more anomalies are detected (see the
    previous histogram's description for the types of anomalies considered),
    *and* once per boot, even if reporting fails.

    So this histogram will be recorded at most once per boot, and only if a
    system is detected as anomalous (i.e. presents any of the tracked
    anomalies.)
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.AppCount2.{AppType}" units="apps"
    expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>
    Records number of {AppType} apps found for a given intent in the Sharesheet
    when the sharesheet is invoked. Has 100 exponential buckets. (The original
    histogram had 1000 linear buckets).

    Warning: this histogram was expired from M95 to M96; data may be missing.
  </summary>
  <token key="AppType">
    <variant name="All" summary="all apps"/>
    <variant name="Arc" summary="arc app"/>
    <variant name="Web" summary="web app"/>
  </token>
</histogram>

<histogram name="ChromeOS.Sharesheet.CopyToClipboard.FormFactor"
    enum="ChromeOSSharesheetFormFactor" expires_after="2023-02-16">
  <owner>melzhang@chromium.org</owner>
  <owner>vpao@google.com</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    Records the form factor when the Copy To Clipboard option is selected from
    the sharesheet.
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.FileCount" units="files"
    expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>
    Records the number of files a user is trying to share from the Sharesheet
    when the sharesheet is invoked.
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.FormFactor"
    enum="ChromeOSSharesheetFormFactor" expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>Records the form factor when the Sharesheet is invoked.</summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.IsDriveFolder" enum="Boolean"
    expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>
    If the value is true, the data being shared from the Sharesheet is a folder
    from Drive. Recorded when the sharesheet is invoked.
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.IsImagePreviewPressed"
    enum="BooleanSelected" expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>
    If the value is true, the image preview was pressed during the current
    invocation. Recorded when the sharesheet closes.
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.LaunchSource"
    enum="ChromeOSSharesheetLaunchSource" expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>
    Records the source from which the Sharesheet is invoked.

    Warning: this histogram was expired from M95 to M96; data may be missing.
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.ShareActionCount"
    enum="ChromeOSSharesheetAction" expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>
    Records each action found for a given intent when the Sharesheet is invoked.

    Warning: this histogram was expired from M95 to M96; data may be missing.
  </summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.UserAction"
    enum="ChromeOSSharesheetAction" expires_after="2022-10-08">
  <owner>dominickn@chromium.org</owner>
  <owner>melzhang@chromium.org</owner>
  <summary>Records user action on sharesheet invocations.</summary>
</histogram>

<histogram name="ChromeOS.Sharesheet.{Location}.MimeType"
    enum="ChromeOSSharesheetMimeType" expires_after="2022-10-08">
  <owner>melzhang@chromium.org</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    Records the mime type of the content being copied at the {Location} point in
    the Sharesheet flow.

    This histogram could record multiple times in a single share in the event
    that the user shares data of mime types at once. However, a single share
    will not record the same mime type twice. E.g. sharing 2 images in one share
    will record the image mimetype once.
  </summary>
  <token key="Location">
    <variant name="CopyToClipboard"
        summary="After copy to clipboard is selected"/>
    <variant name="Invocation" summary="When the sharesheet is first invoked"/>
  </token>
</histogram>

<histogram name="ChromeOS.Sync.PreferencesMigrated" enum="BooleanMigrated"
    expires_after="2022-06-01">
  <owner>rsorokin@chromium.org</owner>
  <owner>jamescook@chromium.org</owner>
  <owner>cros-oac@google.com</owner>
  <summary>
    Tracks whether browser sync preferences were migrated to the new OS sync
    feature (project SplitSettingsSync). Recorded once per session during login.
  </summary>
</histogram>

<histogram base="true" name="ChromeOS.SystemTray.AnimationSmoothness" units="%"
    expires_after="2022-04-13">
<!-- Name completed by histogram suffixes
     name="SystemTrayTransitionType" -->

  <owner>amehfooz@chromium.org</owner>
  <owner>tengs@chromium.org</owner>
  <summary>
    Tracks the animation smoothness for the collapse / expand animation of the
    system tray.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.BlockedNotifiersAfterUpdate"
    units="notifiers" expires_after="2022-05-10">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    Tracks the number of blocked notifiers in the system tray after the user
    blocks one or multiple notifiers. Note that this metric records the number
    of blocked notifiers *after* the update.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.BlockedNotifiersOnOpen" units="notifiers"
    expires_after="2022-05-10">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    Tracks the number of blocked notifiers in the system tray when it is opened.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.FeaturePodCountOnOpen" units="count"
    expires_after="2022-04-01">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    The number of feature pods (e.g. WiFi, Bluetooth, IME, Accessibility, etc.)
    in the system tray quick settings when it is opened, including pods that
    overflow to other pages. See
    ChromeOS.SystemTray.Tablet.FeaturePodCountOnOpen for the corresponding
    histogram logged in tablet mode.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.FirstInteraction"
    enum="CrosSystemTrayFirstInteraction" expires_after="2022-04-01">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    Records the first interaction the user has with the system tray, which can
    be a click/tap on the quick settings or message center bubble. Note that
    this interaction could be at any time after the user opens the tray (e.g. 30
    seconds later before the first click).
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.Interaction"
    enum="CrosSystemTrayInteraction" expires_after="2022-04-01">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    An enum value how system tray bubble is interacted e.g. by tap (touch
    screen), or click (mouse, trackpad, etc.) Reported every time the region
    inside system tray bubble is tapped or clicked.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.IsExpandedOnOpen" enum="Boolean"
    expires_after="2022-05-10">
  <owner>tengs@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    If the value is true, SystemTray is expanded when it's opened. Otherwise,
    it's closed when it's opened.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.NotificationsRemovedByClearAll"
    units="notifications" expires_after="2022-04-01">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    Records the number of notifications that are removed in a single clear all
    action by the user.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.OpenHelpPageForManaged"
    enum="CrosSystemTrayManagedType" expires_after="M83">
  <owner>yamaguchi@chromium.org</owner>
  <summary>
    Type of the support page which user opened by clicking the indicator of
    managed device type in the unified system tray bubble.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.ShelfPodCount" units="count"
    expires_after="2022-04-01">
  <owner>tengs@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in
    the shelf status area whenever a pod appears/disappears. This histogram is
    only logged when the device is not in tablet mode, otherwise
    ChromeOS.SystemTray.Tablet.ShelfPodCount is logged.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.Tablet.FeaturePodCountOnOpen"
    units="count" expires_after="2022-05-10">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    The number of feature pods (e.g. WiFi, Bluetooth, IME, Accessibility, etc.)
    in the system tray quick settings when it is opened, including pods that
    overflow to other pages. This histogram is only logged when the device is in
    tablet mode, otherwise ChromeOS.SystemTray.FeaturePodCountOnOpen is logged.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.Tablet.ShelfPodCount" units="count"
    expires_after="2022-04-01">
  <owner>tengs@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in
    the shelf status area whenever a pod appears/disappears. This histogram is
    only logged when the device is in tablet mode, otherwise
    ChromeOS.SystemTray.ShelfPodCount is logged.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.TimeToClick" units="ms"
    expires_after="2021-08-22">
  <owner>tengs@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    The amount of time a user took from clicking on the button in status area,
    to clicking on an item in the system tray bubble. (Obsolete M90 onwards).
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.TimeToClick2" units="ms"
    expires_after="2022-04-01">
  <owner>tengs@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    The amount of time a user took after opening the system tray bubble, to
    clicking on an item in the system tray bubble.
  </summary>
</histogram>

<histogram name="ChromeOS.SystemTray.ToggleExpanded"
    enum="CrosSystemTrayToggleExpanded" expires_after="2022-05-10">
  <owner>amehfooz@chromium.org</owner>
  <owner>gzadina@google.com</owner>
  <summary>
    An enum value how system tray bubble is expanded or collapsed. It can be
    toggled by the button and touch gesture.
  </summary>
</histogram>

<histogram name="ChromeOS.TypeC.CableSpeed" enum="CableSpeedMetric"
    expires_after="2022-04-30">
  <owner>pmalani@chromium.org</owner>
  <owner>chromeos-power@google.com</owner>
  <summary>
    This value represents the speed of the USB Type-C cable which is connected
    to a device. It is recorded every time a new peripheral is connected.
  </summary>
</histogram>

<histogram name="ChromeOS.TypeC.PartnerType" enum="PartnerTypeMetric"
    expires_after="2022-04-30">
  <owner>pmalani@chromium.org</owner>
  <owner>chromeos-power@google.com</owner>
  <summary>
    This value represents the type of a USB Type-C peripheral (the Partner)
    which is connected to a device. It is recorded every time a new peripheral
    is connected.
  </summary>
</histogram>

<histogram name="ChromeOS.TypeC.WrongConfiguration"
    enum="WrongConfigurationMetric" expires_after="2022-04-30">
  <owner>pmalani@chromium.org</owner>
  <owner>chromeos-power@google.com</owner>
  <summary>
    This value represents events where a USB Type-C peripheral couldn't be
    configured correctly, or experienced some other unexpected behaviour. It is
    recorded every time a new peripheral is connected.
  </summary>
</histogram>

<histogram name="ChromeOS.UrlXattrsCount" units="units"
    expires_after="2022-04-10">
  <owner>jorgelo@chromium.org</owner>
  <owner>tnagel@chromium.org</owner>
  <summary>
    The number of files with URL extended attributes found in the users' home
    directories. This is emitted once per boot. See crbug.com/919486 and
    crbug.com/939386 for more details.
  </summary>
</histogram>

<histogram base="true" name="ChromeOS.USB.DeviceAttached"
    enum="ChromeOSUsbEventTiming" expires_after="2022-09-08">
  <owner>allenwebb@chromium.org</owner>
  <owner>jorgelo@chromium.org</owner>
  <owner>mnissler@chromium.org</owner>
  <summary>Timing and number of USB devices attached.</summary>
</histogram>

<histogram name="ChromeOS.UserTypeByDeviceType.LogSegment"
    enum="UserDeviceMatrix" expires_after="2023-04-24">
  <owner>bmalcolm@chromium.org</owner>
  <owner>cros-client-wa@google.com</owner>
  <summary>
    This value is reported at the start of a user session, and is a 32-bit value
    that reports the primary user account type and the device type (umanaged
    user on managed device, K12 user on an education device, etc.). The upper
    16-bits represent the device type (found at http://shortn/_3iFWcdjy0P), and
    the lower 16-bits represent the user type (found at
    http://shortn/_uK3ZM4pC0a). So a nonprofit user (0x03) on an enterprise
    device (0x02) would be 0x00020003 or 131075.
  </summary>
</histogram>

<histogram name="ChromeOS.WebAPK.{InstallType}.ArcInstallResult"
    enum="WebApkArcInstallResultChromeOS" expires_after="2022-10-14">
  <owner>tsergeant@chromium.org</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    Records the detailed result when WebAPK is installed through ARC. A WebAPK
    is generated and installed when a PWA which supports Web Share Target is
    installed in the browser, and updated when the PWA's manifest updates. This
    histogram records successes/errors in the last step of the WebAPK
    {InstallType} process, when the generated WebAPK is installed in ARC.
  </summary>
  <token key="InstallType">
    <variant name="Install"/>
    <variant name="Update"/>
  </token>
</histogram>

<histogram name="ChromeOS.WebAPK.{InstallType}.Result"
    enum="WebApkInstallResultChromeOS" expires_after="2022-10-14">
  <owner>tsergeant@chromium.org</owner>
  <owner>chromeos-apps-foundation-team@google.com</owner>
  <summary>
    Records the overall final state of a WebAPK {InstallType} operation on
    ChromeOS. A WebAPK is generated and installed when a PWA which supports Web
    Share Target is installed in the browser, and updated when the PWA's
    manifest updates.
  </summary>
  <token key="InstallType">
    <variant name="Install"/>
    <variant name="Update"/>
  </token>
</histogram>

<histogram name="ChromeOS.WXMountCount" units="count"
    expires_after="2022-06-30">
  <owner>jorgelo@chromium.org</owner>
  <owner>chromeos-security-core@google.com</owner>
  <summary>
    Records the number of writable+executable mounts on the system. The count
    itself is updated every 30 seconds, but this metric is reported every two
    hours of runtime. This metric is reported regardless of whether users are
    logged in or not. This metric is only reported on Chrome OS.
  </summary>
</histogram>

</histograms>

</histogram-configuration>

redpajama_set_name: RedPajamaGithub


text:
The Rhodes Brothers Talk WWE Tag Teams, Allie vs. Brandi Rhodes Hype, More on Final "Road to Fight for the Fallen" Series
July 10th, 2019 Marc Middleton AEW News 0 comments
Above is the third and final episode of AEW's "Road to Fight for the Fallen" series, featuring more build for Saturday's Fight for the Fallen event from Jacksonville, FL.
Alex Marvez hypes Saturday's apparent main event with The Young Bucks vs. AEW Executive Vice President Cody Rhodes and Dustin Rhodes, billed as a Dream Tag Team Match. The Rhodes Brothers were interviewed and it was noted that it's been 1,609 days since they teamed up. This will be Dustin's first time going at it with The Bucks, and he noted that he would never say no to Cody asking him to team up, but he really wanted to retire. Dustin added that he's done a little bit of scouting on The Bucks, and their in-ring work kind of scares him. Cody praised them and said they do everything in the ring. Dustin said he respects their abilities but they make fun of people a lot and that gets under his skin.
Cody recalled a recent dinner with AEW officials and TNT network officials. He said AEW President Tony Khan was talking about how good the Rhodes Brothers were, and Khan, as a fan of the Wrestling Observer Newsletter, said they were "critically reviewed well." This praise for the Rhodes Brothers apparently shocked AEW Executive Vice President Kenny Omega. Cody was taken aback by Omega's reaction. Cody said of Omega, "This is the same guy who thinks Taka Michinoku is a legend, but he doesn't know about The Brotherhood, he doesn't know about Dustin and I."
Dustin responded and recalled how the Rhodes Brothers were the first team to defeat The Shield in WWE. He added, "We were the first team to beat The Shield. So, they weren't watching? They didn't see that or is that just bullshit?"
Cody said they weren't watching or they were pretending to not watch, but he was watching all of their top matches on the indies and they are at a disadvantage.
He said, "I was watching all of that. I think me being so familiar with them, they're at a complete disadvantage because they seem to be unfamiliar with us. I mean if you check social media, they're flirting with The Usos regularly. We beat The Usos' ass for like two years straight. So, I think they're at a true disadvantage here. I think people who are Elite fans would absolutely think this is some sort of odd-man pairing, this isn't We were a great tag team. To think mainstream and put your nose down at us because we were on TV making money, screw that. I may be a little more mad about it than I thought."
Dustin then looked at the camera and asked, "Are you that good, Young Bucks?"
"Guess we'll find out," Cody said.
"Yep, we will," Dustin added.
Brandi Rhodes is also featured as she trains for her first AEW match on Saturday, against Allie. Allie appears and they shake hands, then hug, after a few friendly but competitive words. Allie is interviewed and she mentions her run as Impact Knockouts Champion.
AEW Vice President of Business Operations Nik Sobic appears in the video and notes that the venue, Daily's Place, was designed three years ago by AEW owner Shad Khan. Sobic said there's not a bad seat in the whole venue, which is outdoor and usually used for concerts.
This episode also features hype for Sonny Kiss vs. Peter Avalon on the "Buy In" pre-show, and more build for Saturday's event. You can find the updated Fight for the Fallen card by clicking here.
Next article WWE Cancels Live Events Set for Italy
Previous article Jim Ross Book Details and Cover, Adam Page Talks Health Ahead of AEW All Out (Video)
AEW - LiveSource Announcement, Fight for the Fallen Local News Video, Shawn Spears
MJF Injured at AEW Fight for the Fallen
Kenny Omega Reveals New AEW Fight for the Fallen Match


text:
<?php

/**
 * Adds new global settings.
 */
class AllInOnePageSiteConfig extends DataExtension
{

    private static $DEFAULT_EXCLUDE_CALSSES = array('ErrorPage', 'AllInOnePage');
    private static $many_many               = array(
        'AllInOneExludedPages' => 'SiteTree'
    );

    public function updateCMSFields(FieldList $fields)
    {
        $this->SetDefaultExlcuded();
        $ExludedPagesField = new TreeMultiselectField("AllInOneExludedPages", "Exluded Pages", "SiteTree");
        $ExludedPagesField->setDescription("Add any pages here you want to exclude from the allinone page view");
        $fields->addFieldToTab('Root.AllInOne', $ExludedPagesField);
        return $fields;
    }

    public function SetDefaultExlcuded()
    {
        foreach (SiteTree::get()->filter(array('ClassName' => self::$DEFAULT_EXCLUDE_CALSSES, "ID:not" => AllInOneHelper::excludedPageIds())) as $ExcludedPage) {
            $this->owner->AllInOneExludedPages()->Add($ExcludedPage);
        }
    }
}


The beach can be a very magical and spiritual place, where the land and see come together. In fact, its where all four elements converge; Earth (sand), Wind, Fire (sun) and Water. The natural stones that can be found there, remind us of mother nature's glory and the origin of our most beloved stones and crystals. Let this stunning Beach Crystals Bracelet take you to the shore line and feel the crunchy stones and crystals beneath your feet.
Beautifully decorated with stones and crystals that you'd find on the beach.