Using graphite keys to trace traffic - datacratic/rtbkit GitHub Wiki

You may run into situations where the volume of bid requests you expect to see reaching your agents is lower than you expect. When this happens, you need to determine where the bid requests are being dropped within the pipeline. The usual suspects are:

• at the entrance of the exchange connectors
• requests being dropped because the system is in slow mode
• static filters
• augmentors
• dynamic filters
• bid responses not being correctly received from the agents.

Each of these steps can be checked with the following graphite keys:

Exchange Connectors:

• <install>.router.<exchange-connector>.auctionReceived
• <install>.router.<exchange-connector>.auctionStart

Slow Mode:

• drawAsInfinite(<install>.router.monitor.systemInSlowMode)
• <install>.router.monitor.ignoredAuctions

Static Filters:

• sumSeries(<install>.router.accounts.*.filter.intoStaticFilters)
• sumSeries(<install>.router.accounts.*.filter.passedStaticFilters)
• <install>.router.auctionPassedPreprocessing

Augmenters:

• <install>.augmentationLoop.augmentation.request
• <install>.augmentationLoop.augmentation.response
• <install>.augmentationLoop.augmentation.unknown

Dynamic Filters:

• sumSeries(<install>.router.accounts.*.filter.intoDynamicFilters)
• sumSeries(<install>.router.accounts.*.filter.passedDynamicFilters)

Response from the agents:

• <install>.router.bid
• sumSeries(<install>.router.accounts.*.bids)
• sumSeries(<install>.router.accounts.*.bidErrors.*)
• sumSeries(<install>.agents.*.*)
• All the keys that are in CAPS represent messages from the router.