-
Notifications
You must be signed in to change notification settings - Fork 663
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
MG-1965 - Process Event Logs #2057
Open
rodneyosodo
wants to merge
17
commits into
absmach:main
Choose a base branch
from
rodneyosodo:events-svc
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
ianmuchyri
requested changes
Jan 14, 2024
rodneyosodo
force-pushed
the
events-svc
branch
from
January 15, 2024 10:42
4282f24
to
ed03818
Compare
ianmuchyri
requested changes
Jan 15, 2024
10 tasks
rodneyosodo
force-pushed
the
events-svc
branch
3 times, most recently
from
February 12, 2024 20:46
b877d43
to
26ef76a
Compare
rodneyosodo
force-pushed
the
events-svc
branch
6 times, most recently
from
February 26, 2024 16:54
ec76941
to
35c5eb1
Compare
rodneyosodo
force-pushed
the
events-svc
branch
2 times, most recently
from
March 8, 2024 07:59
449f7ac
to
a817162
Compare
rodneyosodo
force-pushed
the
events-svc
branch
6 times, most recently
from
March 18, 2024 09:02
74d1aa5
to
c993b35
Compare
rodneyosodo
force-pushed
the
events-svc
branch
3 times, most recently
from
March 22, 2024 15:36
7c42d98
to
3ac623d
Compare
rodneyosodo
force-pushed
the
events-svc
branch
5 times, most recently
from
April 4, 2024 09:04
3283210
to
1cab6c0
Compare
rodneyosodo
force-pushed
the
events-svc
branch
6 times, most recently
from
June 12, 2024 14:20
c65d282
to
3eb772c
Compare
arvindh123
reviewed
Jun 13, 2024
arvindh123
requested changes
Jun 13, 2024
activitylog/activity.go
Outdated
case ThingEntity: | ||
return "((operation LIKE 'thing.%' AND attributes->>'id' = :entity_id) OR (attributes->>'thing_id' = :entity_id))" | ||
case ChannelEntity: | ||
return "((operation LIKE 'channel.%' AND attributes->>'id' = :entity_id) OR (attributes->>'group_id' = :entity_id))" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rodneyosodo
I could not list channels
create event.
I think this should be group
or we should change in all events to channel
arvindh123
requested changes
Jun 13, 2024
arvindh123
requested changes
Jun 13, 2024
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
- Added attributes and metadata as seperate values of activity. Metadata is normal metadata for an entity while attributes are the other entities from the event for example id, updated_at e.t.c - add entityType which can either be empty or user, group, thing or channel - add query method which generates SQL query depending on the entity type for example is the entity is user we retrieve entities that have id as the entity id and have operation that is prefixed with user. OR events that have user_id as an attribute correcsponding to that entity - update emission and consumption of events. Emit native types for example string slice for tags rather than formating it and also metadata as it is rather than marshalling it first into bytes This contains breaking changes on how events are consumed Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
A normal user can be able to list invitations but they will get only the operation and time it occurred unless you are the platform admin where you can view anything Signed-off-by: Rodney Osodo <[email protected]> Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Signed-off-by: Rodney Osodo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
What type of PR is this?
This is a feature PR because it adds eventlogs service to store history of events
What does this do?
Adds event logs service
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Yes, I have included tests for my changes.
Did you document any new/modified feature?
Yes, I have updated the documentation for the new feature.
Notes