We're using sumo metrics to record user actions throughout our VOD application i.e. recording how long it takes for a user to see a guidance prompt shown to them after selecting a playback item.
Continuing from the example above, we originally sent the following data using the graphite format: playback.vod.firstPrompt 62 1538387840. However, we would like to capture more information around this event to improve data aggregation, so that in the instance of an inefficient user experience we could have improved insight into the issues being faced (i.e. the platform, network latency, etc).
Therefore, we updated to using the Carbon2 data format, and passed additional metaTags to help differentiate the data further. However, we're now running into the issue that each request is not self-contained such that even with different metaTags the playback.vod.firstPrompt metric is being counted as one.
Is it possible for each metric request to appear in the dashboard as self contained rather than being aggregated and added to an average behind the scenes?
Thanks for your time,
Please sign in to leave a comment.