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.

Sign up for GitHub

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

Jump to bottom

[Graph integration] Topology revamp #732

Open
2 of 4 tasks
noboruma opened this issue Dec 7, 2022 · 0 comments · Fixed by #928
Open
2 of 4 tasks

[Graph integration] Topology revamp #732

noboruma opened this issue Dec 7, 2022 · 0 comments · Fixed by #928
Assignees
@noboruma @manV
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration

Comments

@noboruma
Copy link
Collaborator

noboruma commented Dec 7, 2022 •
edited
Loading

As part of the ongoing effort to integrate with neo4j graph (#692) we are revamping the way we report and show topology graph

  • Ingestion
  • Filtering
  • UI
  • Rework clean up to keep Host nodes
@noboruma noboruma added enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration labels Dec 7, 2022
noboruma added a commit that referenced this issue Dec 29, 2022
@noboruma
Fix topology return type #732
73bf8b6
noboruma added a commit that referenced this issue Dec 29, 2022
@noboruma
Ignore neo4j constraints conflicts #732
06f154b
@deviprasad303 deviprasad303 linked a pull request Mar 8, 2023 that will close this issue
V2 resource ingest 2 #928
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@noboruma noboruma

@manV manV

Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

V2 resource ingest 2 deepfence/ThreatMapper
2 participants
@noboruma @manV