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.

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

would like a unique key in event json to simplify ticketing/event aggregation system. #1196

Closed
joshzitting opened this issue Mar 22, 2016 · 8 comments

Comments

Projects
None yet
4 participants
@joshzitting
Copy link

commented Mar 22, 2016

We are sending sensu events to sentry (getsentry.com) for logging/event aggregation. Something that would be useful for us (and I think other people if they try tying sensu into a ticketing system) is a unique value (stored as part of the event output) that is generated/stored on the sensu server on the first 1 or 2 status and remains the same until the status returns to 0.
That way we can categorize/aggregate events based on this value so that a check disk usage % will have the same ticket associated with it from a warning state, to critica,l to resolved...

Thanks!

@creativelycloudy

This comment has been minimized.

Copy link

commented Mar 22, 2016

+1

On Mar 22, 2016, at 6:19 PM, Joshua Zitting notifications@github.com wrote:

We are sending sensu events to sentry (getsentry.com) for logging/event aggregation. Something that would be useful for us (and I think other people if they try tying sensu into a ticketing system) is a unique value that is generated/stored on the sensu server on the first 1 or 2 status and remains the same until the status returns to 0.
That way we can categorize/aggregate events based on this value so that a check disk usage % will have the same ticket associated with it from a warning state, to critica,l to resolved...

Thanks!


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #1196

@calebhailey calebhailey added the Feature label Apr 6, 2016

@calebhailey calebhailey added this to the 0.24 milestone Apr 6, 2016

@calebhailey

This comment has been minimized.

Copy link
Member

commented Apr 6, 2016

Event IDs (uuid values) already exist (although they aren't documented anywhere), however not in a way that would be useful in this context. Currently event IDs are unique to each occurrence of the event, which isn't necessarily incorrect behavior, but it's also not very useful. Furthermore, event IDs are not used anywhere else in Sensu, so there's no reason we can't make event ids more useful by making them correspond to a specific event.

👍

@calebhailey calebhailey added the Small label Apr 6, 2016

@portertech

This comment has been minimized.

Copy link
Member

commented Apr 6, 2016

https://github.com/sensu/sensu/blob/master/lib/sensu/server/process.rb#L447

Make it:

:id => stored_event ? stored_event[:id] : random_uuid,

@portertech

This comment has been minimized.

Copy link
Member

commented Apr 6, 2016

730147c4-7560-11e4-9375-fefd2f67563b

@joshzitting

This comment has been minimized.

Copy link
Author

commented Apr 6, 2016

Sweet! I cant wait for this one to be merged! Thanks guys!!

@calebhailey

This comment has been minimized.

Copy link
Member

commented Apr 9, 2016

Related: #849

@portertech

This comment has been minimized.

Copy link
Member

commented Apr 28, 2016

Just about time to merge #1248 👍

@portertech

This comment has been minimized.

Copy link
Member

commented Apr 28, 2016

#1248 has been merged, the change will be available in the upcoming 0.24 release!

@portertech portertech closed this Apr 28, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.