Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service Connector deployed to chosen compartment with compartment specific metric namespaces #15

Closed
wants to merge 3 commits into from

Conversation

ecout
Copy link

@ecout ecout commented Oct 21, 2024

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.

Einar Coutin added 3 commits October 21, 2024 14:56
… each compartment that are currently present and also those that could be present in the future.
…es. At a minimum combine it with the metric namespaces available in the compartment to get a more comprehensive list.
@kanishktripathi
Copy link
Contributor

This change was incorporated in this release
https://github.com/DataDog/oracle-cloud-integration/releases/tag/datadog-oci-orm-v1.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants