108 results found

1. BQ Lens Access - Account Federation Blocker
   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Development  ·  0 comments  ·  BigQuery Lens  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Regression Line for Reports

   Hi Team,

   I'd like to propose a graphical enhancement to reports visualisation

   Issue Summary:
   When using reports with 2-dimensional graphical chart types (Stacked Columns, Lines, etc) users infer the trends in their costs eyeballing the data as there's no trend (or regression) line describing visually how the data changed over time. This leads to reports lacking information and requiring extra steps to get to the desired information

   Desired Outcome:
   A graphical aid that tells the user if the data is trending upwards or downwards and by how much in an intuitive manner

   Suggested Solution:
   A linear (to keep it computationally light) regression line to be displayed in the chart. It might also be toggled on and off to keep the chart clean

   Hi Team,

   I'd like to propose a graphical enhancement to reports visualisation

   Issue Summary:
   When using reports with 2-dimensional graphical chart types (Stacked Columns, Lines, etc) users infer the trends in their costs eyeballing the data as there's no trend (or regression) line describing visually how the data changed over time. This leads to reports lacking information and requiring extra steps to get to the desired information

   Desired Outcome:
   A graphical aid that tells the user if the data is trending upwards or downwards and by how much in an intuitive manner

   Suggested Solution:
   A linear (to keep it computationally… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Development  ·  0 comments  ·  Cloud Analytics & Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Improved Labelling for Unallocated Costs in EKS Lens Reports

   Salut la Product Team,

   I am writing to request an enhancement to the EKS Lens reporting feature within the [Your Cloud Management Platform Name].
   I have noticed (and I am not the only one) that in the cost reports generated by EKS Lens, there are instances where costs are labeled as "N/A," particularly in relation to the "EC2-Other" category.
   This label is not very convenient for understanding the allocation of costs and can lead to confusion when analysing customers' cloud expenditure.

   Issue Encountered:
   In the Navigator EKS cost reports, it is frequently encountered that a label "N/A" which seems to be associated with costs that cannot be directly attributed to a specific resource or tag. This makes it challenging to fully understand and manage our cloud costs, as we (TAMs, CREs, Customers) cannot easily identify the source or reason for these unallocated expenses.

   Feature Request - what is expected:
   I would like to request the following features to be considered for implementation in EKS Lens:
   - Enhanced labelling mechanism: An improved system for labelling resources that currently fall under the "N/A" category. This could include automated suggestions for labelling based on resource type, usage patterns, or other identifiable characteristics.

   • Customisable label mapping: it would be very useful to be able to define custom label mappings for costs that are not directly attributable to a specific resource or tag. This would allow our customers to categorise and allocate these costs according to their internal accounting practices.

   • Detailed unallocated cost breakdown: A dedicated section or report within EKS Lens that provides a detailed breakdown of unallocated costs, including possible reasons for why they are not labeled and suggestions for how to address this.

   • Labelling policy enforcement: Tools or checks within EKS Lens to ensure that all resources within EKS clusters are labelled according to our organisation's policies, with alerts for any resources that are missing required labels.

   • then we need to teach them how to fish by providing some documentation and best practices for labelling within EKS Lens, including how to handle common scenarios that result in "N/A" labels and strategies for improving cost allocation accuracy.

   Impact:
   Implementing these features would greatly enhance our customers' ability to track and manage cloud costs with precision. It would also provide clarity for their finance and operations teams, enabling them to make more informed decisions based on accurate cost allocation data.

   Conclusion:
   I believe that these enhancements would be beneficial not only to many other users of EKS Lens who are seeking to optimise their cloud cost management practices.

   Merci :)

   Salut la Product Team,

   I am writing to request an enhancement to the EKS Lens reporting feature within the [Your Cloud Management Platform Name].
   I have noticed (and I am not the only one) that in the cost reports generated by EKS Lens, there are instances where costs are labeled as "N/A," particularly in relation to the "EC2-Other" category.
   This label is not very convenient for understanding the allocation of costs and can lead to confusion when analysing customers' cloud expenditure.

   Issue Encountered:
   In the Navigator EKS cost reports, it is frequently encountered that a label "N/A" which seems to… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Development  ·  1 comment  ·  Kubernetes  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Single Email Login for Multiple Domains in DoIT Console

   Hello Bonjour dear Product Team,

   I am reaching out to suggest an enhancement to the DoIT console that would greatly benefit large organisations with multiple BUs, particularly those that have grown through acquisitions.

   Issue Summary:
   Currently, users must log in separately to each domain within the DoIT console to manage cloud resources and costs. This can be cumbersome for teams that oversee cloud management across various business units within a single company. The need to log out and log back in for each domain creates inefficiencies and complicates the management process.

   Desired Outcome:
   We propose the implementation of a feature that allows a single email address to be used for logging into multiple domains within the DoIT console.
   This feature should provide the following capabilities:
   - A unified login experience that grants access to all associated domains without the need to log out and switch accounts.
   - The ability to seamlessly navigate between different domains from a central dashboard, improving the efficiency of cloud management tasks.
   - Enhanced user permission controls to ensure that access to each domain is properly governed and aligned with organisational policies.

   Suggested Solutions:
   - Develop a multi-domain access system that links multiple domains to a single user profile, based on the user's email address.
   - Introduce a domain switcher within the user interface that allows users to toggle between domains they have access to without logging out.
   - Implement robust access controls that allow administrators to define and manage the level of access each user has for each domain.

   Impact:
   The introduction of a single email login for multiple domains would significantly improve the user experience for teams managing complex cloud environments. It would streamline the navigation process within the Navigator/DoIT console, reduce the time spent on administrative login tasks, and encourage wider adoption of the tool.

   This feature is particularly critical for organisations with centralised cloud management teams responsible for multiple business units. By simplifying the login process, we can enhance productivity and ensure that their cloud management efforts are more cohesive and efficient.

   I strongly believe that this enhancement aligns with DoIT's goal of simplifying cloud management and would be a valuable addition to our Navigator.

   Hello Bonjour dear Product Team,

   I am reaching out to suggest an enhancement to the DoIT console that would greatly benefit large organisations with multiple BUs, particularly those that have grown through acquisitions.

   Issue Summary:
   Currently, users must log in separately to each domain within the DoIT console to manage cloud resources and costs. This can be cumbersome for teams that oversee cloud management across various business units within a single company. The need to log out and log back in for each domain creates inefficiencies and complicates the management process.

   Desired Outcome:
   We propose the implementation of a feature… more

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Super Admin Role or Managerial Hierarchy for Reports and Dashboards Management

   Dear Product Team,

   I am reaching out to request the addition of a new feature that would greatly enhance the management capabilities within our customers' engineering teams.
   I have a customer, he is an Engineering Manager, and he has encountered limitations in overseeing and managing the reports, dashboards, and alerts created by members of my team.

   Issue Summary:
   Currently, there is no role or permission set that allows a manager or team lead to view, modify, or edit the reports, dashboards, or alerts created by other team members. This lack of oversight capability hinders effective team management and collaboration, as well as the ability to maintain consistency and accuracy across our customers teams' work.

   What is expected:
   I would like to see the implementation of a Super Admin role or a managerial hierarchy system that would allow managers to have control over their team's reports, dashboards, and alerts (or attributions... everything!).
   This role or system should enable the following functionalities:
   - View all reports, dashboards, and alerts created by team members.
   - Edit or modify these items to ensure they align with team standards and objectives.
   - Manage access permissions for team members to streamline workflow and collaboration.
   - Have an overview of team activity and performance metrics in one centralised location.

   Suggested Solutions:
   - Introduce a Super Admin role with elevated permissions to manage all team-related content.
   and/or
   - Develop an organisational hierarchy feature that mirrors the company's structure, allowing managers to have administrative control over their direct reports' content.

   Impact:
   The addition of this feature would significantly improve the efficiency of our customers' engineering management processes. It would allow for better alignment of team activities, more effective knowledge sharing, and quicker response times to necessary changes in their testing and assessment strategies.

   I believe that many other organisations using would also benefit from this enhanced level of control and oversight.

   Merci :)

   Dear Product Team,

   I am reaching out to request the addition of a new feature that would greatly enhance the management capabilities within our customers' engineering teams.
   I have a customer, he is an Engineering Manager, and he has encountered limitations in overseeing and managing the reports, dashboards, and alerts created by members of my team.

   Issue Summary:
   Currently, there is no role or permission set that allows a manager or team lead to view, modify, or edit the reports, dashboards, or alerts created by other team members. This lack of oversight capability hinders effective team management and collaboration, as… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  2 comments  ·  Users & Roles  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Enhanced Multi-org Email Notification Management

   Hello Product Team,

   I am writing to submit a feature request to address a critical issue we are facing with the management of AWS Root Account email notifications for multiple orgs under our management.

   Issue Summary:
   Currently, when we onboard subsidiaries and assign dedicated AWS Management Account Root email addresses, all notifications are being directed to the same mailbox. This setup results in important notifications being shared across subsidiaries, leading to potential security and privacy concerns. More context on the issue can be found in the related Zendesk ticket: https://doitintl.zendesk.com/agent/tickets/171678

   What is expected :
   We would like a feature that allows us to manage email notifications for each subsidiary independently, ensuring that each organisation receives only the notifications intended for them, without any leakage of information to other subsidiaries.

   Suggested Solutions:
   Implement a way to segregate email notifications at the root level based on the subsidiary.
   Provide a dashboard or tool within the DoIT console that allows for granular control of notification settings for multiple organisations.

   Impact:
   This issue is causing significant concern within our org, as it affects our ability to maintain confidentiality and proper governance across our subsidiaries. It is imperative that we find a solution to manage these notifications effectively and securely.

   Merci :)

   Hello Product Team,

   I am writing to submit a feature request to address a critical issue we are facing with the management of AWS Root Account email notifications for multiple orgs under our management.

   Issue Summary:
   Currently, when we onboard subsidiaries and assign dedicated AWS Management Account Root email addresses, all notifications are being directed to the same mailbox. This setup results in important notifications being shared across subsidiaries, leading to potential security and privacy concerns. More context on the issue can be found in the related Zendesk ticket: https://doitintl.zendesk.com/agent/tickets/171678

   What is expected :
   We would like a feature that… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Alerts for unused BQ tables

   Upon reviewing our usage statistics, we have noticed that there are numerous tables within our BigQuery environment that have been inactive for an extended period, some dating back more than three months. These unused tables are not only occupying valuable storage space but also incurring unnecessary costs for our organization.
   To address this issue proactively, we would like to explore the possibility of setting up a system where your team sends us periodic reminder emails whenever they identify tables that have been inactive for more than three months. This would enable us to review and determine whether these tables are still needed for our business operations. If not, we can take appropriate actions to archive or delete them, thus optimizing our BigQuery usage and reducing costs.

   Upon reviewing our usage statistics, we have noticed that there are numerous tables within our BigQuery environment that have been inactive for an extended period, some dating back more than three months. These unused tables are not only occupying valuable storage space but also incurring unnecessary costs for our organization.
   To address this issue proactively, we would like to explore the possibility of setting up a system where your team sends us periodic reminder emails whenever they identify tables that have been inactive for more than three months. This would enable us to review and determine whether these tables are… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Discovery  ·  0 comments  ·  BigQuery Lens  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Use BQ Lens feature without Advanced company level permissions for DoIT

   I am writing to propose an enhancement to the BQ Lens feature within the DoiT Console. This suggestion stems from our recent experiences and challenges while trying to integrate BQ Lens into our systems at Froomle.

   Current Challenge:
   The BQ Lens feature currently requires granting organization-level permissions to DoiT for data sinking from all projects within an organization. This requirement is not compatible with our company’s security policies, which strictly adhere to the Principle of Least Privileges and Infrastructure as Code (IaC) protocols.

   Proposed Enhancement:
   We propose an alternative approach where clients can manage the data sinking process internally, providing DoiT with access only to specific datasets necessary for the BQ Lens feature. This would allow clients to maintain control over their data and comply with their internal security standards.

   Benefits of the Proposed Enhancement:

   Enhanced Security Compliance: Clients can maintain strict control over data access, aligning with various security frameworks and internal policies.
   Flexibility: Provides a more adaptable solution for clients with different security needs and organizational structures.
   Increased Adoption: This enhancement could encourage wider usage of the BQ Lens feature among clients who are currently hesitant due to security concerns.
   Client Trust: Demonstrates DoiT's commitment to accommodating clients’ security needs, fostering trust and long-term partnerships.
   We believe this enhancement will not only address our current needs but will also be beneficial for other DoiT clients facing similar challenges.

   Thank you for considering this enhancement request. We look forward to a positive response and are willing to provide further details or participate in discussions to expedite this process.

   Best Regards,

   Matthias Verstappen

   I am writing to propose an enhancement to the BQ Lens feature within the DoiT Console. This suggestion stems from our recent experiences and challenges while trying to integrate BQ Lens into our systems at Froomle.

   Current Challenge:
   The BQ Lens feature currently requires granting organization-level permissions to DoiT for data sinking from all projects within an organization. This requirement is not compatible with our company’s security policies, which strictly adhere to the Principle of Least Privileges and Infrastructure as Code (IaC) protocols.

   Proposed Enhancement:
   We propose an alternative approach where clients can manage the data sinking process internally, providing… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  BigQuery Lens  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close