-
Notifications
You must be signed in to change notification settings - Fork 2
Execute Analytic Service for specific network service
efotopoulou edited this page Mar 14, 2019
·
2 revisions
Scope: This functionality is used for realizing an analysis upon the data generated by a network service activity
REST - API: http://profiler_server_IP_address/service/sp/{nsr_id}
nsr_id: the network service record id
POST body parameters
{
"name": "String with the name of the analytic service",
"metrics": "JSONArray. This is an optional field",
"start": "start datetime to fetch timeseries data (eg.2019-03-04T07:30:30.781Z)",
"end": "end datetime to fetch timeseries data (eg.2019-03-04T07:30:30.781Z)"
}
The result of such a call is a JSONArray that contains a set of urls where the end user can see the profiling analysis results.
A response example should be:
[
"http://opencpu_server/ocpu/tmp/x0d8b61dcbe8022/console",
"http://opencpu_server/ocpu/tmp/x0d8b61dcbe8022/files/finaldata.csv",
"http://opencpu_server/ocpu/tmp/x0d8b61dcbe8022/files/metricsCombination.html"
]
- Home
- Architecture
-
APIs
- Get analytic services list
- Get analytic Results list
- Get analytic Service Result
- Get metrics per vnv nsr_id (vnv)
- Get metrics per vnv test results uuid (vnv)
- Execute Analytic Service for vnv test
- Execute Analytic Service for sdk experiment (input from Prometheus)
- Execute Analytic Service for sdk experiment (input from csv)
- Execute Analytic Service for sp network service
- Execute Analytic Service Generic
- Integration with VnV
- Integration with SDK
- Supported Analytic Services
- Local Execution