Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Expected Entries When Running SQL Queries on Grafana Explore #8266

Open
Candice-hub1 opened this issue Jan 14, 2025 · 3 comments
Open
Labels
type/question This issue is a question

Comments

@Candice-hub1
Copy link

Question

When running this command curl 'https://dora-sbg.co.za/api/rest/plugins/org/users.csv' -X 'PUT' -H 'Authorization: Bearer {}' --form 'file=@"/Users/hlatshwayonompumelelo/Desktop/users.csv"' it succeeds, but when I try to retrieve the data from the grafana dashboards explore page using SQL queries it only outputs the last entry of the users.csv file. How can this be resolved?

Screenshots

Image

Additional context

Add any other context here.

@Candice-hub1 Candice-hub1 added the type/question This issue is a question label Jan 14, 2025
Copy link

dosubot bot commented Jan 14, 2025

Hey @Candice-hub1! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's tackle this together!

The issue you're experiencing, where only the last entry of the users.csv file is displayed in Grafana Explore, could be due to several reasons related to data ingestion or query execution. Here are some steps to troubleshoot and resolve the issue:

  1. CSV File Format: Ensure that the users.csv file is correctly formatted. Check for any anomalies such as missing headers, inconsistent delimiters, or improperly quoted fields that might affect data parsing.

  2. Data Ingestion Process: Verify that the data ingestion process is correctly configured. Ensure that the curl command is correctly uploading the entire file and that there are no errors during the upload process. You might want to check the logs for any warnings or errors that could indicate issues during data ingestion.

  3. Database Configuration: Check the database configuration to ensure that it is set up to handle multiple entries. There might be constraints or triggers that are affecting how data is stored.

  4. SQL Query: Double-check the SQL query used in Grafana Explore. Ensure that there are no filters or conditions that might limit the results to a single entry. You can try running the query directly on the database outside of Grafana to see if the issue persists.

  5. Grafana Configuration: Ensure that Grafana is correctly configured to connect to the database and retrieve data. Check the data source settings in Grafana to ensure they are correct.

If these steps do not resolve the issue, consider checking for any known limitations or bugs in the current version of Apache DevLake that might affect data visibility in Grafana Explore. Additionally, reviewing the logs for both Apache DevLake and Grafana might provide more insights into the problem.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@Candice-hub1
Copy link
Author

@dosu where can I check for the logs? I hosted it on aws ecs and rds aurora mysql

Copy link

dosubot bot commented Jan 14, 2025

To check the logs for your setup on AWS ECS and RDS Aurora MySQL, follow these steps:

  1. AWS ECS Logs:

    • Go to the AWS Management Console and navigate to the ECS service.
    • Select your cluster and then the specific task running your application.
    • Under the "Logs" tab, you can view the logs if you have configured logging (e.g., using AWS CloudWatch Logs). Ensure that your ECS task definition includes a log configuration.
  2. AWS RDS Aurora MySQL Logs:

    • In the AWS Management Console, navigate to the RDS service.
    • Select your Aurora MySQL instance.
    • Under the "Logs & events" section, you can view various logs such as error logs, slow query logs, and general logs. Make sure logging is enabled for the logs you need.

If logging is not yet configured, you may need to set up AWS CloudWatch Logs for ECS and enable logging for your RDS instance. This will help you capture and analyze logs for troubleshooting.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question This issue is a question
Projects
None yet
Development

No branches or pull requests

1 participant