[
https://issues.jboss.org/browse/RTGOV-343?page=com.atlassian.jira.plugin....
]
ivan mckinley commented on RTGOV-343:
-------------------------------------
Considerations
- concept for indexing of information in elasticsearch.
-parent child relationship (situation a child of ActvityUnit ect),
- building new index based on service type?
- Sharding of information.
- related situations and activities should route on the same shard. this results in
less overhead on the elasticsearch backend
-
EPN to store activity events, response times and situations in
ElasticSearch
----------------------------------------------------------------------------
Key: RTGOV-343
URL:
https://issues.jboss.org/browse/RTGOV-343
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
Standard EPN deployment for storing activity events and situations in ElasticSearch.
The ActivityUnit (possibly minus the events, although would provide efficient retrieval
of the whole unit) should be stored as one type, the ActivityType derived objects as
another, response times and the situations as their own type.
Build the EPN, but it shouldn't be included in the standard deployment - possibly
have an 'extension' folder in the distribution for optional deployable artifacts
with relevant notes - i.e. so they don't all need to be discussed in the main docs?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira