StackHealh Doc pages V1.0.2 - compact + content check (#938)

* regrouping diagnosis and resolution + fixing content and making it more compact
* se offline update
* issue_se_no_alerts.md update + nano changes internal link in root cause of earlier 2
* lp offline update
* lp no log read + nano update - link
* lp_no_logs_parsed + nano up
* _lp_no_alerts simplificaiton by pointing to se no alert
* rx integ offline update
* fw integ offline update
* link fix

---------

Co-authored-by: jdv <julien@crowdsec.net>

Author: rr404

crowdsec-docs/docs/appsec/quickstart/general.mdx

@@ -179,7 +179,7 @@ This scenario can only be triggered again after a 1-minute delay.
 
 ### Multiple AppSec Configurations
 
-You can [load multiple AppSec configurations](/appsec/vpatch_crs.md) for different rule sets:
+You can [load multiple AppSec configurations](/appsec/vpatch_and_crs) for different rule sets:
 
 ```yaml
 # /etc/crowdsec/acquis.d/appsec.yaml

crowdsec-docs/unversioned/getting_started/installation/whm.mdx

@@ -148,7 +148,7 @@ Most of the time it will be a port conflict or config file error
 - Check the logs for error
   - In CrowdSec's logs sudo less /var/log/crowdsec.log: Note that it might be very verbose.
   - You can also check:  sudo journalctl -u crowdsec
-- Ultimately, you can check the [Security Engine Troubleshooting section](/u/troubleshooting/security_engine.mdx)
+- Ultimately, you can check the [Security Engine Troubleshooting section](/u/troubleshooting/security_engine)
 
 ### Changing port configuration
 

crowdsec-docs/unversioned/getting_started/post_installation/acquisition_troubleshoot.mdx

@@ -21,7 +21,7 @@ The first thing to check is that the log file is found and readable by the Crowd
 
 Within the CrowdSec log file it will log if the file was found or not.
 
-Log file locations change by distribution, you can find the default log location [outlined here](/u/troubleshooting/security_engine.mdx#where-are-the-logs-stored).
+Log file locations change by distribution, you can find the default log location [outlined here](/u/troubleshooting/security_engine#where-are-the-logs-stored).
 
 <FormattedTabs
   bash="grep '/path/to/your/file.log' /var/log/crowdsec.log"

crowdsec-docs/unversioned/getting_started/post_installation/troubleshoot.mdx

@@ -9,7 +9,7 @@ import FormattedTabs from '@site/src/components/formatted-tabs';
 
 # Troubleshoot
 
-This troubleshoot section is intended to help you resolve common issues that may arise during the installation process. You can find extensive [troubleshooting documentation](/u/troubleshooting/intro.md) if this document does not resolve your issues.
+This troubleshoot section is intended to help you resolve common issues that may arise during the installation process. You can find extensive [troubleshooting documentation](/u/troubleshooting/intro) if this document does not resolve your issues.
 
 # Logs and Errors
 
@@ -89,6 +89,6 @@ After you have made the changes you will need to restart the CrowdSec service.
 
 ## Next Steps?
 
-If the above hasn't resolved the issue you are facing, you can find more detailed troubleshooting documentation [here](/u/troubleshooting/intro.md).
+If the above hasn't resolved the issue you are facing, you can find more detailed troubleshooting documentation [here](/u/troubleshooting/intro).
 
 If you have resolved the issue you can continue with the [post installation steps](/getting_started/next_steps.mdx#1-crowdsec-console-).

crowdsec-docs/unversioned/troubleshooting/console_issues.md

@@ -10,22 +10,22 @@ This page lists all possible health check issues, their trigger conditions, and
 
 - 🔥 **Critical**: Immediate attention required - core functionality is impaired
 - ⚠️ **High**: Important issue that should be addressed soon - may impact protection effectiveness
-- 💡 **Recomended**: Additionnal actions that will continue improving your security posture *(comming in next iterations of Stack Health)*
+- 💡 **Recommended**: Additionnal actions that will continue improving your security posture *(comming in next iterations of Stack Health)*
 - 🌟 **Bonus** : Optimization advises and upper tier recommendation with great return on value *(comming in next iterations of Stack Health)*
 
 ## Health Check Issues Overview
 
 | Issue | Criticality | Summary | Resolution |
 |-------|-------------|---------|------------|
-| **Security Engine Offline** | 🔥 Critical | Security Engine has not reported to Console for 24+ hours | [Troubleshooting](/u/troubleshooting/issue_se_offline) |
-| **Security Engine No Alerts** | ⚠️ High | No alerts generated in the last 48 hours | [Troubleshooting](/u/troubleshooting/issue_se_no_alerts) |
-| **Security Engine Too Many Alerts** | ⚠️ High | More than 250,000 alerts in 6 hours | [Troubleshooting](/u/troubleshooting/issue_se_too_many_alerts) |
-| **Log Processor Offline** | 🔥 Critical | Log Processor has not checked in with LAPI for 24+ hours | [Troubleshooting](/u/troubleshooting/issue_lp_offline) |
-| **Log Processor No Alerts** | ⚠️ High | Log Processor has not generated alerts in 48 hours | [Troubleshooting](/u/troubleshooting/issue_lp_no_alerts) |
-| **Log Processor No Logs Read** | 🔥 Critical | No logs acquired in the last 24 hours | [Troubleshooting](/u/troubleshooting/issue_lp_no_logs_read) |
-| **Log Processor No Logs Parsed** | 🔥 Critical | Logs read but none parsed in the last 48 hours | [Troubleshooting](/u/troubleshooting/issue_lp_no_logs_parsed) |
 | **Integration for Firewall Offline** | 🔥 Critical | Firewall has not pulled from BLaaS endpoint for 24+ hours | [Troubleshooting](/u/troubleshooting/issue_integration_fw_offline) |
 | **Integration for RC Offline** | 🔥 Critical | Remediation Component has not pulled from endpoint for 24+ hours | [Troubleshooting](/u/troubleshooting/issue_integration_rc_offline) |
+| **Log Processor No Alerts** | ⚠️ High | Log Processor has not generated alerts in 48 hours | [Troubleshooting](/u/troubleshooting/issue_lp_no_alerts) |
+| **Log Processor No Logs Parsed** | 🔥 Critical | Logs read but none parsed in the last 48 hours | [Troubleshooting](/u/troubleshooting/issue_lp_no_logs_parsed) |
+| **Log Processor No Logs Read** | 🔥 Critical | No logs acquired in the last 24 hours | [Troubleshooting](/u/troubleshooting/issue_lp_no_logs_read) |
+| **Log Processor Offline** | 🔥 Critical | Log Processor has not checked in with LAPI for 24+ hours | [Troubleshooting](/u/troubleshooting/issue_lp_offline) |
+| **Security Engine No Alerts** | ⚠️ High | No alerts generated in the last 48 hours | [Troubleshooting](/u/troubleshooting/issue_se_no_alerts) |
+| **Security Engine Offline** | 🔥 Critical | Security Engine has not reported to Console for 24+ hours | [Troubleshooting](/u/troubleshooting/issue_se_offline) |
+| **Security Engine Too Many Alerts** | ⚠️ High | More than 250,000 alerts in 6 hours | [Troubleshooting](/u/troubleshooting/issue_se_too_many_alerts) |
 
 ## Issue Dependencies
 

crowdsec-docs/unversioned/troubleshooting/intro.md

@@ -21,9 +21,9 @@ If you received a health check alert from the CrowdSec Console, check out the [*
 
 ## Troubleshooting by Topic
 
-* [Security Engine Troubleshooting](/u/troubleshooting/security_engine.mdx)
-* [Remediation Components Troubleshooting](/u/troubleshooting/remediation_components.mdx)
-* [CTI Troubleshooting](/u/troubleshooting/cti.mdx)
+* [Security Engine Troubleshooting](/u/troubleshooting/security_engine)
+* [Remediation Components Troubleshooting](/u/troubleshooting/remediation_components)
+* [CTI Troubleshooting](/u/troubleshooting/cti)
 
 ## Community support