-
Notifications
You must be signed in to change notification settings - Fork 626
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
No reports available for "domain" type #469
Comments
Do you have the complete screenshot of the observable details page? |
I have a similar issue except it's for all types rather than just domains. OS: Ubuntu 16.04 If you need any more information, please let me know. |
@znb @LetMeR00t we'll prioritize this. Please provide the complete screenshot of the observable details page as requested by @nadouani. |
I am not seeing any report tags either after the upgrade to 3.0.4 |
@saadkadhi Not sure if it's related, but I'm seeing this error in my application.log file https://gist.github.com/znb/db509c60f17832d9924033039270f702 Looks like I'm getting a 500 back from Elasticsearch. |
same issue here |
Question: do you see the mini reports on the observable details page? |
Well, this question is useless, the observable details page displays the same mini reports as the observables list. So it's the same issue, you should not see them in the details page. This is a regression from #409 |
I know, the jobs are listed, but I can also see that the "mini reports" that are supposed to be displayed below the observable name, and above the "metadata" bloc, are not display, which is a bug coming from the same reason of the original issue. |
Yes :) |
This issue is a regression introduced by #409. It is solved by Elastic4play 1.4.4 (TheHive-Project/elastic4play#49) |
After the last update I have the same behaviour on every Observable. |
Request Type
Bug
Work Environment
Problem Description
As you can see on the following screen shots, I have no report available for the given domain whereas I have some reports available when I click on it.
The text was updated successfully, but these errors were encountered: