We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
dashboards
No
When using Elastic Packetbeat Flows data the following error shows up with a Sankey visualization:
Error: Sankey is a DAG, the original data has cycle!
Example Event:
{ "@timestamp": "2018-11-15T14:41:24.000Z", "agent": { "hostname": "host.example.com", "name": "host.example.com", "version": "8.13.3" }, "destination": { "bytes": 460, "ip": "198.51.100.2", "mac": "06-05-04-03-02-01", "packets": 2, "port": 80 }, "event": { "dataset": "flow", "duration": 3000000000, "end": "2018-11-15T14:41:24.000Z", "start": "2018-11-15T14:41:21.000Z" }, "flow": { "final": true, "id": "FQQA/wz/Dv//////Fv8BAQEBAgMEBQYGBQQDAgGrAMsAcQPGM2QC9ZdQAA", "vlan": 171 }, "network": { "bytes": 470, "community_id": "1:t9T66/2c66NQyftAEsr4aMZv4Hc=", "packets": 3, "transport": "tcp", "type": "ipv4" }, "source": { "bytes": 10, "ip": "203.0.113.3", "mac": "01-02-03-04-05-06", "packets": 1, "port": 38901 } }
For the Sankey visualization I am using the following fields:
No response
N/a
Latest
The text was updated successfully, but these errors were encountered:
Related apache/echarts#19505
This is a known issue with Apache Echarts, I'm not sure why it happens with my data though.
Sorry, something went wrong.
ktx-kirtan
No branches or pull requests
Which OpenObserve functionalities are the source of the bug?
dashboards
Is this a regression?
No
Description
When using Elastic Packetbeat Flows data the following error shows up with a Sankey visualization:
Error: Sankey is a DAG, the original data has cycle!
Example Event:
For the Sankey visualization I am using the following fields:
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the version you discovered this bug in (check about page for version information)
Anything else?
No response
The text was updated successfully, but these errors were encountered: