Diagnostic is the Schema for the Diagnostics API. Manages an API Management Service Diagnostic.
Type
CRD
Group
apimanagement.azure.upbound.io
Version
v1beta1
apiVersion: apimanagement.azure.upbound.io/v1beta1
kind: Diagnostic
DiagnosticSpec defines the desired state of Diagnostic
No description provided.
Reference to a Logger in apimanagement to populate apiManagementLoggerId.
Policies for referencing.
Selector for a Logger in apimanagement to populate apiManagementLoggerId.
Policies for selection.
Reference to a Management in apimanagement to populate apiManagementName.
Policies for referencing.
Selector for a Management in apimanagement to populate apiManagementName.
Policies for selection.
A backend_request block as defined below.
A backend_response block as defined below.
A frontend_request block as defined below.
A frontend_response block as defined below.
Reference to a ResourceGroup in azure to populate resourceGroupName.
Policies for referencing.
Selector for a ResourceGroup in azure to populate resourceGroupName.
Policies for selection.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
A backend_request block as defined below.
A backend_response block as defined below.
A frontend_request block as defined below.
A frontend_response block as defined below.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
DiagnosticStatus defines the observed state of Diagnostic.
No description provided.
A backend_request block as defined below.
A backend_response block as defined below.
A frontend_request block as defined below.
A frontend_response block as defined below.
Conditions of the resource.
applicationinsights
apiVersion: apimanagement.azure.upbound.io/v1beta1
kind: Diagnostic
metadata:
annotations:
meta.upbound.io/example-id: apimanagement/v1beta1/diagnostic
labels:
testing.upbound.io/example-name: example
name: applicationinsights
spec:
forProvider:
alwaysLogErrors: true
apiManagementLoggerIdSelector:
matchLabels:
testing.upbound.io/example-name: example
apiManagementNameSelector:
matchLabels:
testing.upbound.io/example-name: example
backendRequest:
- bodyBytes: 32
headersToLog:
- content-type
- accept
- origin
backendResponse:
- bodyBytes: 32
headersToLog:
- content-type
- content-length
- origin
frontendRequest:
- bodyBytes: 32
headersToLog:
- content-type
- accept
- origin
frontendResponse:
- bodyBytes: 32
headersToLog:
- content-type
- content-length
- origin
httpCorrelationProtocol: W3C
logClientIp: true
resourceGroupNameSelector:
matchLabels:
testing.upbound.io/example-name: example
samplingPercentage: 5
verbosity: verbose
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.