Advertisement
Guest User

Untitled

a guest
Feb 10th, 2016
61
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.94 KB | None | 0 0
  1. Tracking Delayed Metrics Senders
  2.  
  3. If the collectionTime of a metric payload is older than 5 minutes, we term it as a delayed metric. We would want to track who is the tenant responsible for sending delayed metrics to us with the JMX tracking in Blueflood.
  4.  
  5. There is a script in the blueflood-chef repo that enables tracking of delayed metrics.
  6. After cloning the blueflood-chef, cd into the contrib directory and run the script. The usage is as follows.
  7. ./blueflood_tenant_tracker.sh myusername track_delayed_start app00.iad.prod.bf.k1k.me
  8.  
  9. You can also do prod_all (but generally only one node is enough to display who are the delayed metrics senders)
  10. ./blueflood_tenant_tracker.sh myusername track_delayed_start prod_all
  11.  
  12. In Kibana logs you will now be able to see something like this:
  13. [TRACKER][DELAYED METRICS] Tenant sending delayed metrics is 706456
  14.  
  15. To stop tracking
  16. ./blueflood_tenant_tracker.sh myusername track_delayed_stop app00.iad.prod.bf.k1k.me
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement