×
API Usage Dashboard
This dashboard presents all requests to the Rucio API that have been originated by the selected account (top of the page). Users can use this to conveniently debug their scripts or identify potential optimizations in terms of resource efficiency.
Activity Over Time
In this bar plot, the request rate and their response code are illustrated.
HTTP Status Codes
For those who are not familiar with HTTP status codes
[1]:
- 2xx: Everything is fine.
- 4xx: Your fault. Maybe you asked for something that doesn't exist?
- 5xx: Our fault, sorry.
Detailed information about the HTTP status codes returned by the Rucio API can be found here
[2]. If one is only interested in a certain HTTP code (e.g., 404 Not Found), clicking inside the plot (not the legend!) allows to filter only for matching data. To disable or reverse the filter use the bubbles at the top of the dashboard, or use the browser's back button.
Selecting Time Frames
For convenience, at the top of the page, a few predefined historical time frames are listed, starting from 15 minutes up to 4 days. If one is interested in a specific timeframe, just click-and-hold in the graph to zoom into the custom time frame. Use the browsers back button to zoom out again.
Over All Numbers
This provides some absolute numbers about the workload.
- Count: Absolute number of requests during the selected time frame.
- Unique Client IPs: In case your script is distributed, this shows on how many hosts it is executed. This can be especially useful to identify faulty hosts (e.g. 409 errors coming from the same IP).
- Sum Bytes Input: The sum of the network traffic caused by submitting requests to Rucio.
- Sum Bytes Output: The sum of the network traffic caused by receiving the response from Rucio.
- Sum Duration: Number of milliseconds Rucio was busy serving the requests. Each request is timed from the first character arriving till the both ends were closed again.
Resources
The actual resources that have been requested together with a counter, time in milliseconds, and input/output bytes. For details about the different URIs and how a client might call them see the Rucio REST-API documentation
[2].
It also provides a script name (scriptID). This is the name of the file with the first CLI argument appended. Especially useful to identify a rogue cronjob or similar.
Links
[1]
HTTP Status Codes: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
[2]
Rucio REST-API Documentation: http://rucio.cern.ch/REST_Intro.html