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

Add reporting to elasticsearch #462

Open
ResistanceIsUseless opened this issue Jun 2, 2023 · 2 comments
Open

Add reporting to elasticsearch #462

ResistanceIsUseless opened this issue Jun 2, 2023 · 2 comments
Labels
Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@ResistanceIsUseless
Copy link

Please add an option to export responses to elasticsearch, similar to nuclei.

It would be nice to have two levels of reporting:

  • just crawled paths (similar to if you did something like | jq .endpoint)
  • full response
  • request and response might also be useful
@ResistanceIsUseless ResistanceIsUseless added the Type: Enhancement Most issues will probably ask for additions or changes. label Jun 2, 2023
@ehsandeep
Copy link
Member

@ResistanceIsUseless thanks! we will work on common implementation to support this in all / applicable projects.

@gedw99
Copy link

gedw99 commented Aug 19, 2023

You might want to try zinc. It’s a pure golang elastic search which is about 100 tomes less resource intensive. It’s pretty easy and can be clustered and use s3 or local for storage.

https://github.com/zincsearch/zincsearch

Its a simple go get and oyu have the server, cli and web gui. NIce and easy.
Its fast too.

it’s well supported too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

No branches or pull requests

3 participants