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

Aggregate events with groupby returning no data #2149

Open
mschoenb97IL opened this issue Sep 9, 2024 · 3 comments
Open

Aggregate events with groupby returning no data #2149

mschoenb97IL opened this issue Sep 9, 2024 · 3 comments

Comments

@mschoenb97IL
Copy link

Describe the bug

The Python code example from https://docs.datadoghq.com/api/latest/logs/#aggregate-events is not returning any data. I know that this is not due to my project not containing any data for this query. If you remove the "groupby" field in the LogsQueryFilter, it does return data.

I tried with many different groupby facets, and had no success.

To Reproduce
Steps to reproduce the behavior:

Run the Python example from https://docs.datadoghq.com/api/latest/logs/#aggregate-events. This used to return data but no longer does.

Expected behavior

Something like the following will be printed:

{'data': {'buckets': []},
 'meta': {'elapsed': XXX,
          'request_id': '...",
          'status': 'done'}}

Environment and Versions (please complete the following information):

Running on version 2.28.0

@mschoenb97IL
Copy link
Author

Ah, I got data by removing the total="recall" from the groupby example. The docs should probably be updated

@christi3k
Copy link

Just confirming that I also hit this issue with version 2.28.0 and that removing total=recall resolved it.

Copy link

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of this project.

  2. Comment that the issue is still reproducible and include updated details requested in the issue template.

@github-actions github-actions bot added the stale label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants