-
Notifications
You must be signed in to change notification settings - Fork 8
/
prolexic-analytics.yaml
259 lines (259 loc) · 8.02 KB
/
prolexic-analytics.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
openapi: 3.0.0
info:
title: Prolexic Analytics
version: '2'
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
servers:
- url: https://{hostname}/prolexic-analytics/v2
- url: http://prolexic-analytics/v2
x-akamai:
auth-type: EDGE_GRID
file-path: prolexic-analytics.yaml
paths:
/attack-report/contract/{contract}/attack-id/{attackId}:
parameters:
- $ref: parameters/attackId-path.yaml
- $ref: parameters/contract-path.yaml
get:
operationId: get-attack-report-contract-contract-attack-id-attackid
summary: Get an attack report
tags:
- Attack reports
description: |
Retrieves an attack report for the specified customer and `attackId`.
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/attack_report.json
schema:
$ref: schemas/AttackReport.yaml
403:
description: |
Unauthorized request.
content:
application/json:
example:
$ref: examples/error403.json
404:
description: |
Not found.
content:
application/json:
example:
$ref: examples/error404.json
/attack-reports/contract/{contract}/start/{start}/end/{end}:
parameters:
- $ref: parameters/end-path.yaml
- $ref: parameters/start-path.yaml
- $ref: parameters/contract-path.yaml
get:
operationId: get-attack-reports-contract-contract-start-start-end-end
summary: List attack reports
tags:
- Attack reports
description: |
Retrieves a list of attack reports for a customer within the specified time range.
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/attack_reports_get.json
schema:
$ref: schemas/AttackReports.yaml
403:
description: |
Unauthorized request.
content:
application/json:
example:
$ref: examples/error403.json
404:
description: |
Not found.
content:
application/json:
example:
$ref: examples/error404.json
/critical-events/contract/{contract}:
parameters:
- $ref: parameters/contract-path.yaml
get:
operationId: get-critical-events-contract-contract
summary: List critical events
tags:
- Critical events
description: |
Retrieves a critical events list for a customer.
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/critical_events_get.json
schema:
$ref: schemas/CriticalEvent.yaml
403:
description: |
Unauthorized request.
content:
application/json:
example:
$ref: examples/error403.json
404:
description: |
Not found.
content:
application/json:
example:
$ref: examples/error404.json
/events/contract/{contract}:
parameters:
- $ref: parameters/contract-path.yaml
get:
operationId: get-events-contract-contract
summary: List events
tags:
- Events
description: |
Retrieves an events list for a customer.
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/events_get.json
schema:
$ref: schemas/EventResponse.yaml
403:
description: |
Unauthorized request.
content:
application/json:
example:
$ref: examples/error403.json
404:
description: |
Not found.
content:
application/json:
example:
$ref: examples/error404.json
/metric-types/{contract}:
parameters:
- $ref: parameters/contract-path.yaml
get:
operationId: get-metric-types-contract
summary: List metric types
tags:
- Metric types
description: |
Retrieve a list of metric types for a specific customer.
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/metric-types.json
schema:
$ref: schemas/MetricType.yaml
403:
description: |
Unauthorized request.
content:
application/json:
example:
$ref: examples/error403.json
404:
description: |
Not found.
content:
application/json:
example:
$ref: examples/error404.json
/metrics:
post:
operationId: post-metrics
summary: Get metrics data
tags:
- Metrics
description: |
Lists metrics specified in the `type` object, falling between given `start` and `end` times, sampled at the given rate and attached to given contract. The maximum range between start and end is 90 days. If some (not all) requested types are invalid, invalid types are silently dropped, and the response only contains data for valid requests. More meaningful errors result if you are requesting data for only one type at a time.
requestBody:
required: true
content:
application/json:
example:
$ref: examples/metrics_post_req.json
schema:
$ref: schemas/MetricDataInput.yaml
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/metrics_response.json
schema:
$ref: schemas/MetricResponse.yaml
403:
description: |
Unauthorized request.
content:
application/json:
example:
$ref: examples/error403.json
404:
description: |
Not found.
content:
application/json:
example:
$ref: examples/error404.json
/time-series-data:
get:
operationId: get-time-series-data
summary: Get time series data
tags:
- Time series data
description: |
Lists usage and attack information for individual destination IP addresses. Optionally specify the `startTime` and `endTime` to get data from a specific period. The maximum date range is the last seven days and by default you get data from the last two hours. Specify `locations` to include only traffic coming through specific data centers, or `source` for specific router types. Indicate the `samplingSize` to determine the number of timestamps to get data for. Enable `sum` to get aggregated data.
parameters:
- $ref: parameters/destinations-query.yaml
- $ref: parameters/endTime-query.yaml
- $ref: parameters/locations-query.yaml
- $ref: parameters/samplingSize-query.yaml
- $ref: parameters/source-query.yaml
- $ref: parameters/startTime-query.yaml
- $ref: parameters/sum-query.yaml
responses:
200:
description: |
Successful response.
content:
application/json:
example:
$ref: examples/TimeSeriesDataResponse.json
schema:
$ref: schemas/TimeSeriesDataFeatureSchema.yaml
400:
description: |
Bad request.
500:
description: |
Internal error.