-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support retrieving available product areas for services via api/v2/services/catalog/product_areas
#1666
Comments
api/v2/services/catalog/product_areas
api/v2/services/catalog/product_areas
Thanks for your contribution! This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community. If you would like this issue to remain open:
|
Still a valid request |
Thanks for your contribution! This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community. If you would like this issue to remain open:
|
Note:
If you have a feature request, you should contact support so the request can be properly tracked.
Is your feature request related to a problem? Please describe.
We want to track which services use which products of DD, therefore we would like to query this at once.
Using the browser dev console, we have identified that endpoint which seems to deliver the needed data.
Describe the solution you'd like
Implement the respective endpoint
Describe alternatives you've considered
The alternative is using our service catalog and try to fetch data for each product ( APM, RUM, host ). That would lead to at least 3x number of services API requests instead of single one.
Additional context
No additional context.
The text was updated successfully, but these errors were encountered: