Documentation updates

Author: andytael

docs-source/site/docs/deploy/buildpushapp.md

@@ -68,3 +68,8 @@ If the build and push is successful, you should get a message similar to this:
 [INFO] Finished at: 2025-09-24T12:18:53-05:00
 [INFO] ------------------------------------------------------------------------
 ```
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/deploy/dbaccess.md

@@ -10,6 +10,15 @@ This step is only necessary if your application is connecting to a database.
 
 If your application needs database access, first obtain the database user credentials. Then create a Kubernetes secret containing those credentials. The secret is referenced in your application deployment.
 
+:::note Namespace Configuration
+All `kubectl` commands in this guide use `-n obaas-dev` as an example namespace. Replace `obaas-dev` with your actual application namespace in all commands.
+
+To verify your namespaces, run:
+```bash
+kubectl get namespaces
+```
+:::
+
 ### Create the secret for the application
 
 Create a secret with database access information. This secret is used by the application configuration and is injected during deployment.
@@ -177,3 +186,8 @@ spec:
         secret:
           secretName: obaas-adb-tns-admin-1
 ```
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/deploy/deployapp.md

@@ -59,3 +59,8 @@ obaas:
   - `EUREKA_CLIENT_FETCH_REGISTRY`
   - `EUREKA_CLIENT_SERVICE_URL_DEFAULTZONE`
   - `EUREKA_INSTANCE_HOSTNAME`
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/deploy/introflow.md

@@ -30,3 +30,8 @@ To deploy an application to OBaaS, follow this high-level workflow:
 - Update Chart.yaml with the application name.
 - Update values.yaml to match your configuration.
 - Install the Helm chart.
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/intro.md

@@ -37,3 +37,8 @@ Deploy on Oracle Cloud Infrastructure, other cloud providers, or hybrid environm
 ### Simplified Operations
 
 OBaaS vastly simplifies the task of building, testing, and operating microservices platforms. From development through production, automated workflows and integrated tooling streamline every phase of the application lifecycle.
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/observability/acces.md

@@ -4,14 +4,23 @@ sidebar_position: 2
 ---
 ## How to access SigNoz
 
-1. Get the _admin_ email and password for SigNoz. Replace the example namespace `observability` with the namespace where SigNoz is deployed.
+:::note Namespace Configuration
+All `kubectl` commands in this guide use `-n observability` as the default namespace. If SigNoz is installed in a different namespace, replace `observability` with your actual namespace name in all commands.
+
+To find your namespace, run:
+```bash
+kubectl get pods -A | grep signoz
+```
+:::
+
+1. Get the _admin_ email and password for SigNoz:
 
    ```shell
    kubectl -n observability get secret signoz-authn -o jsonpath='{.data.email}' | base64 -d
    kubectl -n observability get secret signoz-authn -o jsonpath='{.data.password}' | base64 -d
    ```
 
-1. Expose the SigNoz user interface (UI) using this command. Replace the example namespace `observability` with the namespace where SigNoz is deployed:
+1. Expose the SigNoz user interface (UI) using this command:
 
    ```shell
    kubectl -n observability port-forward svc/obaas-signoz-frontend 3301:3301
@@ -20,3 +29,8 @@ sidebar_position: 2
 1. Open [SigNoz Login](http://localhost:3301/login) in a browser and login with the _admin_ email and the _password_ you have retrieved.
 
 ![SigNoz UI](images/obaas-signoz-ui.png)
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/observability/configure.md

@@ -205,3 +205,8 @@ It also adds the `OTEL_EXPORTER_OTLP_ENDPOINT` to pod environment variables for
 - name: OTEL_EXPORTER_OTLP_ENDPOINT
   value: http://obaas-signoz-otel-collector.observability:4318
 ```
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/observability/dashboards.md

@@ -197,3 +197,8 @@ Details about Transaction Manager for Microservices(https://docs.oracle.com/en/d
 
 ![MicroTx Dashboard](images/microtx-dashboard.png)
 
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).
+

docs-source/site/docs/observability/dbexporter.md

@@ -1,9 +1,49 @@
 ---
-title: Oracle Database Metrics Exporter 
+title: Oracle Database Metrics Exporter
 sidebar_position: 6
 ---
 ## Oracle Database Metrics Exporter
 
-Oracle Database Metrics Exporter aims to provide observability for the Oracle Database so that users can understand performance and diagnose issues easily across applications and the database. Oracle Database Metrics Exporter delivers functionality to support both cloud and on-premises databases, including those running in Kubernetes and containers.
+The Oracle Database Metrics Exporter is a key observability component that provides comprehensive metrics collection for Oracle Database. It helps users understand database performance and diagnose issues easily across applications and the database, supporting both cloud and on-premises deployments, including databases running in Kubernetes and containers.
 
-See the [documentation](https://oracle.github.io/oracle-db-appdev-monitoring/) for how to install and configure Oracle Database Metrics Exporter.
+:::info Complete Documentation Available
+This exporter is documented in detail in the **[Platform Components](../platform/dbexporter.md)** section. For complete installation instructions, testing procedures, troubleshooting guidance, and dashboard configuration, please refer to the comprehensive guide:
+
+**[→ Oracle Database Metrics Exporter - Full Documentation](../platform/dbexporter.md)**
+:::
+
+## Quick Links
+
+- **[Installation Guide](../platform/dbexporter.md#installing-oracle-database-metrics-exporter)** - Enable and deploy the exporter
+- **[Testing Guide](../platform/dbexporter.md#testing-oracle-database-metrics-exporter)** - Verify metrics collection
+- **[Dashboards](../platform/dbexporter.md#dashboards)** - View pre-built Grafana dashboards
+- **[Troubleshooting](../platform/dbexporter.md#troubleshooting)** - Common issues and solutions
+- **[Official Documentation](https://github.com/oracle/oracle-db-appdev-monitoring)** - Oracle's GitHub repository
+
+## What Metrics Are Available
+
+The exporter provides Prometheus-formatted metrics including:
+
+- **Database connectivity** - `oracledb_up` - Database instance reachability
+- **Session metrics** - `oracledb_sessions_*` - Active sessions and session statistics
+- **Tablespace metrics** - `oracledb_tablespace_*` - Tablespace usage and capacity
+- **Activity metrics** - `oracledb_activity_*` - Database activity and performance
+- **Transactional Event Queue metrics** - TxEventQ throughput and queue statistics
+
+These metrics are exposed on port 9161 and automatically scraped by Prometheus when properly configured.
+
+## Integration with OBaaS Observability
+
+The Database Metrics Exporter integrates seamlessly with the OBaaS observability stack:
+
+1. **Prometheus** automatically discovers and scrapes metrics from the exporter
+2. **SigNoz** provides pre-built dashboards for visualizing database performance
+3. **Service Discovery** ensures metrics are collected from all database instances
+4. **Alert Manager** can trigger alerts based on database metric thresholds
+
+For the complete setup and configuration, see the **[full documentation](../platform/dbexporter.md)**.
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).

docs-source/site/docs/observability/metricslogstraces.md

@@ -37,3 +37,8 @@ Traces can be filtered based on Service, HTTP Routes etc. Click on a trace to se
 ![SigNoz Traces Details](images/signoz-traces-details.png)
 
 Logs for a trace event can directly be accessed using the _Go to related logs_ link.
+
+## Getting Help
+
+- [#oracle-db-microservices Slack channel](https://oracledevs.slack.com/archives/C06L9CDGR6Z) in the Oracle Developers slack workspace.
+- [Open an issue in GitHub](https://github.com/oracle/microservices-datadriven/issues/new).