add data handling of agent life cycles and events #780
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks great! :) |
Xylus
added a commit
that referenced
this pull request
Jul 28, 2015
add data handling of agent life cycles and events
|
Thanks! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add agent life cycle and event handling support mentioned in #84 to the Collector.This pull request only includes the receiving and storing part of the agent life cycle / event data, retrieval and querying for these data is not included yet.
2 tables were added to the HBase backend - one for agent life cycle, and one for agent events.
This implementation tracks the agent's connect / ping / disconnect events to determine the latest status of a single life cycle of the agents.
These life cycle events are also put into the event table to provide a separate history of events generated to/from the agent.