-
Notifications
You must be signed in to change notification settings - Fork 64
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
Bug: Live dashboard - attribute with tags #171
Comments
For test you could as well create an event with a single attribute that has a tag attache to it. It's not integrated in the live dashboard due to the error above as well |
Some update in the debug process
Or So what we want is a string that we can parse with
We get: this result:
Then adding See Below full render function of the index.js
|
ISSUE FIXED I will open a pull request but in case it's not accepted, you just have to do few changes:
by this:
By this:
|
Hello,
Steps to reproduce
1°) Have a
zmq dashboard
that works with./diagnostic.py
not showing error. (Help you with\logs\*.log
files and )2°) Add the CERT-FR MISP feed to the misp instance. Then fetch/pull misp events from this source (only 13 events pulled).
3°)
./clean.py
for clearing the misp dashboard to remove any data that could come from the fetch.4°) Go to the "[CERT-FR] Le groupe cybercriminel Silence" event then click on the left side panel
Publish event to zmq
.Actual behavior
On the dashboard i see only one attribute integrated.


And in the browser console, i see a long list of this error:
The error is located here line 345 of the
misp-dashboard/static/js/index.js
(file):Debug
I tried to find where the error comes from then i found that:
data is an object of this form:
console.dir(data) --> Object { name: "Tag", data: Array [ "[object Object]" ] }
Object.keys(data.data[0]) --> [ "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", … , "14]
then with this function:
I've got this result for
data.data[0].keys = value
:But i don't know where data.data[0] object is initialized
The text was updated successfully, but these errors were encountered: