Hi there,
Please forgive the questions from a Splunk n00b, but I have not been able to find what I need thus far.
I am writing an A/B testing framework for our site. Originally we thought we'd use StatsD to emit logging data from the framework for our analyses. But, we already have and love Splunk and it makes the most sense to use it instead, and make use of its statistical analysis capabilities.
So, with the C# API, my questions are:
Should there only be one instance of the Service for the lifetime of the .NET App? Is the Service object threadsafe or do I need to handle that manually?
What sorts of traffic can be thrown at the Service? I will want to be sending the equivalent of StatsD's "Counter" data (just log a +1 next to an event). On busy pages we can implement sample rating (e.g. 10% of requests), but there is still the potential for a high volume of calls going to Splunk. What are the implications here?
If Splunk were to go down while the API is sending requests, will the Service handle this or will it cause the .NET app to hang? Is the Service using a fire-and-forget method or not?
Also - should I be using the Service object or the WebClient object?
Apologies for the list of questions - help is most appreciated!
Thanks.
-Will
... View more