-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Elasticsearch support #12
Comments
@sv2 Thanks for awesome work ! I am excited to contribute to this feature enhancement. May I know, how can I start contributing code? |
Thank you, @viswanathreddy - would appreciate your help ! to start, how about you look at creating a test to validate that data is stored in Elasticsearch? one of existing tests can be used as an example. Feel free to open pull request with your test. Thanks ! |
Addressed in v0.95.0 |
Store request/response record in ElasticSearch. Each request/response record to be individual document in the index. Index name to be time-based : sws-YYYY.MM.DD. Document structure and index template to be compatible with packetbeat http document, extending it with additional api-specific properties.
The text was updated successfully, but these errors were encountered: