Skip to content

DoiT Cloud Intelligence

Welcome to the DoiT Cloud Intelligence Customer Feedback Portal.

Please help us improve our product by providing feedback or ideas for new features.  Your input helps us improve our offerings and we pride ourselves on responding and reacting to ideas across our customer base.  When leaving an idea, please be as specific as possible about the problem you are encountering and what your ideal solution looks like.  

Thank you in advance for your comments
If you have any questions please file a ticket in our Console

DoiT Cloud Intelligence

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

3 results found

  1. Can we have an API method to get a ticket by ticket ID with all the metadata and comments?

    For internal DoiT usage, can we have this working just with a ticket # since they are unique across customers? For example:
    curl --request GET \
    --url 'https://api.doit.com/support/v1/tickets/id' \
    --header 'Authorization: Bearer API_KEY' \
    --header 'accept: application/json'

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  APIs  ·  Admin →

    Validated with Yuval Drori, and we have decided to close this user story. It is a "nice to have," so we have created ticket CMP-35234 which will be included in our backlog, waiting to be prioritized when resources are available or when there are more relevant use cases.

  2. It would be great if we could set the Cost Anomaly Detection on Attributes via API and therefore terraform.

    We manage our DoIt Attributes and Groups via terraform and want to avoid any manual configuration.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  APIs  ·  Admin →

    Tried to follow up with requestor and the account team with no response. Closing out this request because it lacks details on the requirement.

  3. Issue: trying to query large and granular datasets from the Billing data source.
    This is not possible without pagination since the rate limit and payload size limit are insufficient to do it in scale.
    Pagination is already implemented in other endpoints in the analytics API but not in the endpoint that will be most affected by it.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  0 comments  ·  APIs  ·  Admin →
  • Don't see your idea?