Service Connector deployed to chosen compartment with compartment specific metric namespaces #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per Support Case: https://help.datadoghq.com/hc/en-us/requests/1893022?page=1 there max limits in the Service Connector Compartment: a maximum of 5 Compartments and a maximum metric namespace of 50.
In this pull request instead of deploying the service connector resource to monitor the root/tenancy compartment, switch it to monitor compartment where the resources live using the data source oci_monitoring_metrics grouped by namespace to extract the supported namespaces from the chosen compartment by compartment id rather than the local.connector_metric_namespaces hardcoded input.