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

Riemann integration #12

Open
mhluongo opened this issue Sep 30, 2014 · 6 comments
Open

Riemann integration #12

mhluongo opened this issue Sep 30, 2014 · 6 comments
Assignees

Comments

@mhluongo
Copy link
Member

No description provided.

@mhluongo
Copy link
Member Author

mhluongo commented Feb 8, 2015

Send a Riemann event

  • per refresh
  • per creation
  • per modifcation
  • per destruction
  • per node refresh, with details about the list

@mhluongo
Copy link
Member Author

mhluongo commented Feb 8, 2015

Config will look like

{:riemann {:protocol :tcp
                  :host "127.0.0.1"
                  :port 5555
                  :tls? true
                  :key "...PKCS8 key..."
                  :cert "..PEM cert..."
                  :ca-cert "...signing CA cert..."
                  :cache-dns? false}}

@mhluongo
Copy link
Member Author

mhluongo commented Feb 9, 2015

Details we want to easily extract:

  • what does the current session pool look like?
    • size?
    • reserved %?
    • browser distribution?
    • % of each tag
  • error rate
  • some idea of session contention
  • the last time we heard from shale

@mhluongo
Copy link
Member Author

mhluongo commented Feb 9, 2015

@chris-martin anything to add here?

@chris-martin
Copy link
Contributor

Maybe an alert if a session has stayed reserved for too long (like >20 minutes) because something has probably failed to unreserve it?

@mhluongo
Copy link
Member Author

mhluongo commented Feb 9, 2015

Session reservation length would be handy as well - average and per session.

mhluongo added a commit that referenced this issue Feb 10, 2015
Since these are reported every session refresh, they're a good target
for use as a service heartbeat.

Refs #12.
mhluongo added a commit that referenced this issue Feb 10, 2015
Since these are reported every session refresh, they're a good target
for use as a service heartbeat.

Refs #12.
mhluongo added a commit that referenced this issue Feb 11, 2015
@staifa staifa self-assigned this Mar 2, 2017
@DrSplinter DrSplinter self-assigned this Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants