I'm migrating from a graphite install and I'm trying to figure out the best way to design a measurement for capturing performance metrics for an application that will allow me to break down performance for specific URLs (or controllers, etc...)
So assume I have a url, and a time in ms it took to handle that url, I plan on saving this to a measurement called "url_performance". My first question is - should I send that information to statsd/telegraf and have it process/summarize those metrics (such as generating count, lower, mean, upper, etc) - or should I just write each measurement directly to influxdb and use native influxdb functions to compute those computed values if I want them. What are the considerations for one over the other? I'm leaning towards just writing this data directly to influxdb The second question is - what are the consideration for implementing the url as a tag vs a field. I want to search by the url (even searching by regex to lump urls together), so that would suggest a tag, but our application could have thousands of unique urls, so the cardinality is perhaps high. So right now, I'm thinking of this simple measurement url_performance tag: url field: ms What troubles will I run into? Thanks! -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/b8671a64-c862-4f0a-8531-483ac70e57e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
