package google.cloud.gkehub.servicemesh.v1alpha

Get desktop application:
View/edit binary Protocol Buffers messages

AnalysisMessage is a single message produced by an analyzer, and it used to communicate to the end user about the state of their Service Mesh configuration.

Used in: FeatureState, MembershipState

• optional AnalysisMessageBase message_base = 1

  Details common to all types of Istio and ServiceMesh analysis messages.

• string description = 2

  A human readable description of what the error means. It is suitable for non-internationalize display purposes.

• repeated string resource_paths = 3

  A list of strings specifying the resource identifiers that were the cause of message generation. A "path" here may be: * MEMBERSHIP_ID if the cause is a specific member cluster * MEMBERSHIP_ID/(NAMESPACE\/)?RESOURCETYPE/NAME if the cause is a resource in a cluster

• optional protobuf.Struct args = 4

  A UI can combine these args with a template (based on message_base.type) to produce an internationalized message.

AnalysisMessageBase describes some common information that is needed for all messages.

Used in: AnalysisMessage

• optional AnalysisMessageBase.Type type = 1

  Represents the specific type of a message.

• AnalysisMessageBase.Level level = 2

  Represents how severe a message is.

• string documentation_url = 3

  A url pointing to the Service Mesh or Istio documentation for this specific error type.

The values here are chosen so that more severe messages get sorted higher, as well as leaving space in between to add more later See istio.analysis.v1alpha1.AnalysisMessageBase.Level

Used in: AnalysisMessageBase

• LEVEL_UNSPECIFIED = 0

  Illegal. Same istio.analysis.v1alpha1.AnalysisMessageBase.Level.UNKNOWN.

• ERROR = 3

  ERROR represents a misconfiguration that must be fixed.

• WARNING = 8

  WARNING represents a misconfiguration that should be fixed.

• INFO = 12

  INFO represents an informational finding.

A unique identifier for the type of message. Display_name is intended to be human-readable, code is intended to be machine readable. There should be a one-to-one mapping between display_name and code. (i.e. do not re-use display_names or codes between message types.) See istio.analysis.v1alpha1.AnalysisMessageBase.Type

Used in: AnalysisMessageBase

• string display_name = 1

  A human-readable name for the message type. e.g. "InternalError", "PodMissingProxy". This should be the same for all messages of the same type. (This corresponds to the `name` field in open-source Istio.)

• string code = 2

  A 7 character code matching `^IST[0-9]{4}$` or `^ASM[0-9]{4}$`, intended to uniquely identify the message type. (e.g. "IST0001" is mapped to the "InternalError" message type.)

**Service Mesh**: State for the whole Hub, as analyzed by the Service Mesh Hub Controller.

Used in: v1alpha.CommonFeatureState

• repeated AnalysisMessage analysis_messages = 1

  Output only. Results of running Service Mesh analyzers.

**Service Mesh**: State for a single Membership, as analyzed by the Service Mesh Hub Controller.

Used in: v1alpha.MembershipFeatureState

• repeated AnalysisMessage analysis_messages = 1

  Output only. Results of running Service Mesh analyzers.