Enable Personalized Service Health for a project using Config Connector
Stay organized with collections
Save and categorize content based on your preferences.
This document explains how to enable a project for service health events
processing using Config Connector
programmatically, if you're using Kubernetes and want to use the
Service Health API.
Follow the prerequisites
for using Config Connector.
Decide on the API VERSION: v1 or v1beta.
Create a file named psh-enable.yaml and copy the following snippet into it:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-03 UTC."],[],[]]