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

Elasticsearch support #12

Closed
sv2 opened this issue Aug 24, 2017 · 3 comments
Closed

Elasticsearch support #12

sv2 opened this issue Aug 24, 2017 · 3 comments
Assignees
@sv2
Labels
enhancement

Comments

@sv2
Copy link
Collaborator

sv2 commented Aug 24, 2017

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.
@sv2 sv2 self-assigned this Aug 24, 2017
@sv2 sv2 added this to v1.0.0 in swagger-stats Aug 24, 2017
@sv2 sv2 mentioned this issue Aug 25, 2017
Closed
@sv2 sv2 moved this from v1.0.0 to 0.90.3 in swagger-stats Sep 2, 2017
@sv2 sv2 moved this from 0.90.3 to 0.91.0 in swagger-stats Sep 23, 2017
@sv2 sv2 moved this from 0.91.0 to v1.0.0 in swagger-stats Sep 28, 2017
@sv2 sv2 moved this from v1.0.0 to 0.90.4 in swagger-stats Oct 24, 2017
@sv2 sv2 moved this from 0.94.0 to v1.0.0 in swagger-stats Nov 7, 2017
@sv2 sv2 moved this from v1.0.0 to 0.95.0 in swagger-stats Nov 11, 2017
@viswanathreddy
Copy link

@sv2 Thanks for awesome work ! I am excited to contribute to this feature enhancement. May I know, how can I start contributing code?

@sv2
Copy link
Collaborator Author

sv2 commented Dec 2, 2017

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 !

sv2 added a commit that referenced this issue Dec 5, 2017
@sv2
#12
3b140ae
sv2 added a commit that referenced this issue Dec 7, 2017
@sv2
index template - #12
bb9a656
sv2 added a commit that referenced this issue Dec 12, 2017
@sv2
Elasticsearch test - #12
03dd1fb
sv2 added a commit that referenced this issue Dec 13, 2017
@sv2
Elasticsearch Dashboard - #12
8b87267
sv2 added a commit that referenced this issue Dec 14, 2017
@sv2
Elasticsearch Dashboard - #12
ed1ba30
sv2 added a commit that referenced this issue Dec 15, 2017
@sv2
Elasticsearch Dashboard - #12
28a700c
@sv2
Copy link
Collaborator Author

sv2 commented Dec 28, 2017

Addressed in v0.95.0

@sv2 sv2 closed this as completed Dec 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sv2 sv2

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@viswanathreddy @sv2