RHIDP-8709: Scorecard plugin (#1465)

* Scorecard plugin

* Incorporated tech changes

* Ihor's and some minor changeS

* Updated Abstract

* Dominika's comments - some of them

* Incorporated Dominika's comments and added images

* Dominika's comments

* Minor changes

* Incorporated Dominika's comments and rebased branch

* Incorporated some of the test day comments

* Fixing build issue

* Test day updates

* Test day updates

* test day minor change

* Incorporated Dominika's comments

* Incorporated Shipra's comments

* Incorporated Shipra's comments

* Minor changes

Author: pabel-rh

artifacts/attributes.adoc

@@ -168,3 +168,6 @@
 :upgrading-book-title: Upgrading {product}
 :using-dynamic-plugins-book-link: {product-docs-link}/html-single/installing_and_viewing_plugins_in_red_hat_developer_hub/index
 :using-dynamic-plugins-book-title: Using dynamic plugins
+
+:scorecard-plugin-book-link: {product-docs-link}/html-single/understanding_and_visualizing_red_hat_developer_hub_project_health_using_scorecards/index
+:scorecard-plugin-book-title: Understanding and visualizing {product} project health using Scorecards

artifacts/snip-developer-preview.adoc renamed to artifacts/snip-developer-preview-lightspeed.adoc

@@ -0,0 +1,6 @@
+[IMPORTANT]
+====
+This section describes Developer Preview features in the Scorecard plugin. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
+
+For more information about the support scope of Red Hat Developer Preview features, see https://access.redhat.com/support/offerings/devpreview/[Developer Preview Support Scope].
+====

artifacts/snip-developer-preview-scorecard.adoc

@@ -0,0 +1,14 @@
+:_mod-docs-content-type: ASSEMBLY
+
+[id="assembly-configuring-scorecards-in-rhdh"]
+= Installing and configuring Scorecards to view metrics in your {product} instance
+:context: assembly-configuring-scorecards-in-rhdh
+
+You can install and configure the following Scorecards to display metrics and visual health status for software components in the {product-very-short} catalog:
+
+* GitHub Scorecards
+* Jira Scorecards
+
+include::modules/observe/scorecards/proc-configuring-github-scorecards-in-rhdh-instance.adoc[leveloffset=+1]
+
+include::modules/observe/scorecards/proc-configuring-jira-scorecards-in-rhdh-instance.adoc[leveloffset=+1]

assemblies/assembly-configuring-scorecards-in-rhdh.adoc

@@ -0,0 +1,29 @@
+:_mod-docs-content-type: ASSEMBLY
+
+[id="assembly-rhdh-observability"]
+= Understanding and visualizing {product} project health using Scorecards
+:context: assembly-scorecards-rhdh
+
+include::modules/observe/scorecards/con-understand-scorecard-plugins.adoc[leveloffset=+1]
+
+include::modules/observe/scorecards/ref-supported-metrics-providers.adoc[leveloffset=+2]
+
+include::assembly-setting-up-scorecards-to-monitor-your-rhdh-health.adoc[leveloffset=+1]
+
+include::assembly-configuring-scorecards-in-rhdh.adoc[leveloffset=+1]
+
+include::modules/observe/scorecards/con-manage-metric-thresholds-in-scorecard-plugin.adoc[leveloffset=+1]
+
+include::modules/observe/scorecards/con-how-thresholds-work.adoc[leveloffset=+2]
+
+include::modules/observe/scorecards/ref-supported-threshold-expressions.adoc[leveloffset=+2]
+
+include::modules/observe/scorecards/ref-threshold-rules-to-metrics-for-scorecard-plugin.adoc[leveloffset=+2]
+
+include::modules/observe/scorecards/con-set-global-standards-for-metric-thresholds.adoc[leveloffset=+2]
+
+include::modules/observe/scorecards/ref-override-rules-to-configure-entity-specific-thresholds.adoc[leveloffset=+2]
+
+include::modules/observe/scorecards/con-best-practices-for-threshold-rules.adoc[leveloffset=+2]
+
+include::modules/observe/scorecards/proc-viewing-scorecards-in-rhdh.adoc[leveloffset=+1]

assemblies/assembly-scorecards-rhdh.adoc

@@ -0,0 +1,9 @@
+:_mod-docs-content-type: ASSEMBLY
+
+[id="assembly-setting-up-scorecards-to-monitor-your-rhdh-health"]
+= Setting up Scorecards to monitor your {product} project health
+:context: assembly-setting-up-scorecards-to-monitor-your-rhdh-health
+
+include::modules/observe/scorecards/proc-installing-scorecard-plugin-in-rhdh-instance.adoc[leveloffset=+1]
+
+include::modules/observe/scorecards/proc-authenticating-and-managing-scorecard-plugins.adoc[leveloffset=+1]

assemblies/assembly-setting-up-scorecards-to-monitor-your-rhdh-health.adoc

@@ -3,7 +3,7 @@
 [id="con-about-developer-lightspeed_{context}"]
 = About {ls-short}
 
-include::{docdir}/artifacts/snip-developer-preview.adoc[]
+include::{docdir}/artifacts/snip-developer-preview-lightspeed.adoc[]
 
 This early access program enables customers to share feedback on the user experience, features, capabilities, and any issues encountered. Your input helps ensure that {ls-short} better meets your needs when it is officially released and made generally available.
 

images/rhdh/scorecard-create-role.png

@@ -0,0 +1,33 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="con-best-practices-for-threshold-rules"]
+= Best practices for threshold rules
+
+Threshold rule evaluation is order-dependent. You must follow logical ordering to avoid unintended category assignments, as the system stops evaluation once a value matches the first rule.
+
+== Follow logical ordering
+
+Rules must be sequenced logically. Order rules from the most strict (smallest range) to the least strict (largest range) or ensure all ranges are mutually exclusive.
+
+=== Problematic rule order example
+
+If rules are ordered incorrectly, a less restrictive rule can prevent stricter rules from being evaluated:
+
+. `warning: <50`: Any value less than 50 triggers the warning rule and stops evaluation.
+. `success: <10`: This rule is not evaluated because all values less than 10 have already matched the preceding warning rule.
+
+=== Correct ordering example
+
+Order the rules from the most restrictive value range to the least restrictive to ensure a logical flow.
+
+[source,yaml]
+----
+# Correct Example: Order from most restrictive (Success) to least restrictive (Error)
+rules:
+  - key: success
+    expression: '<10'     # Only values below 10
+  - key: warning
+    expression: '10-50'   # Only values between 10 and 50
+  - key: error
+    expression: '>50'     # All remaining values above 50
+----