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

docs: bad subcategory name for IBM Cloud Monitoring and IBM Cloud Metrics Routing #5889

Open
sean-freeman opened this issue Dec 19, 2024 · 0 comments

Comments

@sean-freeman
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

New or Affected Resource(s) or Datasource(s)

  • ibm_metrics_router_route
  • ibm_metrics_router_settings
  • ibm_metrics_router_target
  • DS: ibm_metrics_router_routes
  • DS: ibm_metrics_router_targets

Description

The product is "IBM Cloud Monitoring":

Which is confusing when the end-user searches the documentation of the Terraform Provider and cannot find monitoring routes, and when cross-referencing is more confusing given IBM Cloud Metrics Routing is considered separate even though it is under the monitoring section:

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

No branches or pull requests

1 participant