Feature Requests

Teams across the organization have expressed the need for a notification feature tied to scorecards. This feature would trigger alerts when predefined thresholds are exceeded, enabling quicker responses to disruptions and enhancing overall operational efficiency. Context: This requirement emerged as a recurring need across teams. Currently, there is no proactive mechanism to monitor scorecard thresholds, resulting in delayed responses to critical issues. Expected Functionality: Ability to define threshold levels for specific scorecard metrics. Real-time or near real-time notifications when thresholds are breached. Notifications delivered through existing communication channels (e.g., Slack, email, Pager duty). Configurable alert settings to cater to various team requirements. Impact: Faster response times to scorecard disruptions. Increased operational efficiency and collaboration. Reduced risk of missing critical thresholds in performance monitoring. Reduced manual work with automations and manual checks. Request: Please consider prioritizing this feature in upcoming development cycles, as it addresses a critical operational need consistently reported by multiple teams.

Currently, there is no Chronosphere plugin or integration available within Harness IDP. While requirements for this feature are not fully defined, teams have expressed interest in incorporating Chronosphere capabilities into the IDP to centralize monitoring and streamline workflows. Why It Matters: Integrating Chronosphere with Harness IDP would allow teams to monitor metrics and performance data directly within their existing platform, enhancing operational visibility and reducing the need for context-switching between tools. Request: Investigate team requirements and potential use cases for Chronosphere integration within Harness IDP. Explore the feasibility of building a Chronosphere plugin or enabling integration with the IDP for monitoring metrics and dashboards. Impact if Addressed: Centralizes monitoring workflows, making key Chronosphere metrics accessible within Harness IDP. Improves team efficiency by streamlining access to monitoring tools and reducing context-switching.

The Confluence Search Plugin, previously available, has not been migrated to the new Backstage Backend system. As a result, teams are unable to access Confluence content directly within the IDP, impacting productivity and ease of access to documentation. Why It Matters: Accessing Confluence content seamlessly within Harness IDP is critical for enabling teams to find documentation quickly and efficiently. The lack of this feature has been highlighted as a pain point by several teams, who now need to leave the platform to search for resources externally. Request: Coordinate with the plugin owners to assess the feasibility of migrating the Confluence Search Plugin to the new Backstage Backend system. If external plugin owners cannot provide support, consider implementing an internal solution to restore this functionality based on team needs. Impact if Addressed: Improves developer productivity by centralizing access to Confluence documentation within Harness IDP. Enhances user experience by reducing the need to switch between tools, keeping workflows streamlined.

It would be good if we can have NOT operator supported for grabbing the components in a score card. For example if we tag FedRampExclude we can just grab give me all services NOT FedRampExclude to be part of the scorecard.

It would be useful if we can have a notification to slack or email, that a score card for a particular service has change on a daily or weekly basis. This is important especially if a scorecard went from 100% to 50% for example. Or if a scorecard has been fixed from 50% to 100%. This is especially useful as each component may be owned by separate developer group. This was requested by datarobot.

Having the ability to add customisations when working with software templates would help massively. Being able to add improved validation and filtering to help verify and manipulate the inputs of users is important, especially when moving towards more complex templates. See https://backstage.io/docs/features/software-templates/writing-templates#custom-filters-and-globals https://backstage.io/docs/features/software-templates/writing-custom-field-extensions

The current scorecard checks exhibit a binary nature, where each check is either fully completed or not at all. For instance, with two checks on a scorecard, each worth 50 points, the possible scores are limited to 0, 50, or 100. Introducing a "progressive weight" option would enhance this system. For example, if a check allows a maximum of 5 high alerts, having more than 5 alerts would result in a score of 0. However, if there are 3 high alerts, the score should be calculated as follows: (weight%) - (weight% * (actual value / maximum value)). This approach would be applicable to conditions involving less than or greater than operators. These operators would also require the optimal value, where the percentage would be completely fulfilled. In theory this check can be broke down in: less than 5 alerts -weight 10 less than 4 alerts -weight 10 less than 3 alerts -weight 10 less than 2 alerts -weight 10 less than 1 alerts -weight 10 But there could be a predefined setting to make this possible.

On the github data source there's the option to query code scanning alerts by it's severity, however sometimes this is not enough since some tools have higher importance than others. I would suggest to add the tool name as a filter option to allow for a more granular checks and better scorecards.

Files can be uploaded directly into a workflow. If the user wants to extract and use the content of the uploaded file, they need to decode the base64 encoding, as file contents are automatically encoded in base64 when uploaded to workflows. To utilize the file content, a script must be written to decode the base64 encoding based on the file's input format. This functionality could be implemented as a native step in the IDP stage. The step would process the contents of the uploaded file within the workflow and provide the file content as output in its original format.

we are Integrating Dynatrace with IDP components so we need components list in dropdown for particular loggedin user in template UI to select particular component to update, for that we only show them list of componets which has user permission to update not all components list.