dosubot[bot] commented on issue #7808:
URL:
https://github.com/apache/incubator-devlake/issues/7808#issuecomment-2261553587
<!-- Answer -->
The DevLake database is stored in either MySQL or PostgreSQL as of version
0.11. Since you mentioned that the default filepath was set to PVC (Persistent
Volume Claim), the data is stored in a persistent volume managed by Kubernetes.
To access the database, you need to connect to the MySQL or PostgreSQL
instance using the appropriate client. Here are the steps to verify and access
the database:
1. **Check the PVC Configuration**:
Ensure that the PVC is correctly configured in your Helm chart values.
The relevant parameters for MySQL are:
```yaml
mysql.storage.type: pvc
mysql.storage.class: ""
mysql.storage.size: 5Gi
```
2. **Access the MySQL Database**:
Use a MySQL client to connect to the database. You can use the following
command to connect:
```sh
mysql -u merico -p'merico' -h 127.0.0.1 -P 3306 lake
```
3. **Verify Database Tables**:
Once connected, you can check the tables in the `lake` database:
```sql
SHOW TABLES;
```
If the `SHOW TABLES` command returns no tables, it might indicate an issue
with the data ingestion or migration process. However, since you can still see
the data in Grafana, it suggests that the data might be stored in a different
schema or there might be a discrepancy between the database and Grafana views.
Discrepancies between the database and Grafana views could be caused by:
- **Data Sync Issues**: The data sync frequency defined in the Blueprint
might not be frequent enough.
- **Transformation Errors**: Errors in the data transformation process.
- **Customization Errors**: Custom SQL queries or dashboard customizations
might introduce errors or misrepresentations of the data
<sup>[[1]](https://github.com/apache/incubator-devlake/blob/main/README.md)</sup><sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/docs/Overview/Introduction.md)</sup><sup>[[3]](https://github.com/apache/incubator-devlake/blob/main/grafana/dashboards/EngineeringOverview.json)</sup>.
Ensure that the data ingestion process is running correctly and that the
migration scripts have been executed successfully. You can check the
`migration_history` table to verify the state of the database schema
<sup>[[4]](https://github.com/apache/incubator-devlake-website/blob/main/docs/DeveloperManuals/DBMigration.md)</sup><sup>[[5]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v1.0/DeveloperManuals/DBMigration.md)</sup><sup>[[6]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.15/DeveloperManuals/DBMigration.md)</sup><sup>[[7]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.18/DeveloperManuals/DBMigration.md)</sup><sup>[[8]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.19/DeveloperManuals/DBMigration.md)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
