If the start_time parameter is set then it will return up to 100 logs from the specified start time. If you wish to retrieve the latest data for a number of traces, consider using the Get Latest Data command instead If the start_time parameter is omitted then the system will return the latest log. Returns JSON object containing data for the specified trace. Includes the trace id's that are needed for requesting data Parameters Parameter Hidden graphs and traces will be suppressed if the user does not have access to them, otherwise they will include 'graph_hidden' or 'trace_hidden' if hidden. Returns JSON object containing graph objects for the given site_id.Įach object should contain the 'graph_id', 'graph_name', 'graph_sort_order' and an array of traces that include 'trace_id', 'trace_name', 'trace_order'. JSON object containing a base64 encoded image along with a '_links' object containing 'prev' / 'next' links to retrieve additional images (where available) for the given 'site_id'. Optional id if requesting a specific image
We do not allow retrieval of images based on the 'image_id' alone.
If no 'image_id' is provided then it will get the latest available image.Ī 'site_id' must always be provided for security reasons. Returns JSON object containing a base64 encoded image along with a '_links' object containing 'prev' / 'next' links to retrieve additional images (where available) for the given 'site_id'. List of sites that your API key has access to, includes site id's that can be used in other commands. Optional flag to include all site options when set to 1 (default: 0) Setting the optional parameter 'include_all_options=1' will return the other options related to each site.
#Harvest app json password#
Returns JSON object containing an array of site objects for sites that the given API Key or User Name & Password has specific access to.īy default the site object will contain a 'site_options' object with an array of 'locations' for the site. You may also see errors if you fail to adhere to the rate limits Your requests may result in errors if you fail to include required parameters (these will be noted by the command type and the required column). The intended usage is for you to implement the requests server side, at this point you will be able to utilise the likes of AJAX to make a call to your own server which will then access the Harvest API. The Harvest API is not intended to be used from within client side script such as Javascript as this will open up your API key for others to view, as such we have not added headers to allow CORS (attempts to do so in browsers such as Chrome will throw an error, typically something like " Access to XMLHttpRequest at URL from origin YourWebServer has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource". I'm still amazed by how much we can do using Harvest + Graphite.All requests need to contain the output_type parameter, this should be set to application/json for now.Īll requests need to contain the api_key parameter, this should be set to your API key, if you don't have one please contact Harvest Support. We DO have sum and avg functions in Graphite.Ī: summarize(netapp.perf.$Group.$Cluster.svm.$SVM.vol.$Volume.qos_latency_from_throttle, '1h', 'sum', false)ī: summarize(netapp.perf.$Group.$Cluster.svm.$SVM.vol.$Volume.qos_latency_from_throttle, '1h', 'avg', false)Ĭ: alias(divideSeries(#A, #B), 'Throttled samples')
It turns out that we can do this in graphite using built in functions because of a piece of grade school math that I should have remembered before posting. IE: The number of minutes in which some throttling of the volume has taken place over the range in question.Either aggregated by harvest into a rate of some sort, or just a counter that I could do T2 - T1 to get a value for a period.Number of samples in which latency_from_throttle (DELAY_CENTER_QOS_LIMIT) is non-zero in a given period of X samples.Since we're adding to your feature request list Chris, what I'd find really useful is to be able to add to this dashboard would be: I use this to demonstrate to users, the impact that a given qos policy is having on their volume(s). It superimposes the current day/period's values on this and then shows the latency breakdown by these service centers. It shows the range of activity and the mean for iops/latency/throughput by time of day for the past N days. The attached dashboard is useful in seeing the impact of QoS policies on volume I/O, and current volume I/O relative to the past 2 weeks.
0 kommentar(er)
