Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
API call refers to the process of requesting a specific action from the Cocktail server.
The API response is the data received from the server as a result of the requested Cocktail operation
code
string
Internal Response Status Codes
Successful case: 200
result
The type varies depending on the requested task
Contents of the query
status
string
Internal response status
code
string
Value: ""
message
string
Value: ""
metadata
string
Value: null
result
The type varies depending on the requested task
Contents of the query
status
string
Internal response status
Value: "ok"
code
string
Internal Response Status Code
message
string
Internal Response Status Message
status
string
Internal Response Status
Access [External APIs] - [APIs], then click on the "Issued" button.
Fill in the [Issue Token] window, fill in the required information, and then click the "Save" button.
The information to be filled in is as follows
Name*
Token name (non-editable)
Description
Description of the token
Expiration Date
Indefinite or specific date designation
Allow IP
- List of allowed IP addresses - CIDR notation is allowed - Allow all IPs if left blank
Block IP
Blocked IP list
Enter the IP address and press Enter to complete the input
CIDR notation allowed
If the same IP is listed in the allowed IP list, it will be blocked instead
Request Limit
No input or 0 indicates unlimited
Unlimited cannot be modified.
Range*
Click the checkbox to set the permission scope
Click [OK] in the "Save?" popup window, then please check the issued token
Click on the icon to copy the token.
Cocktail Open API is a management service for external access to the Cocktail service API, including features such as user authentication, restrictions, and statistics
This document explains all available API calls and the properties of the returned objects
This is how the Gateway and Cocktail API operate using JWT tokens
Anyone with the API token can use the Cocktail API.
Be careful not to expose the token!
The parameters related to monitoring are as follows
clusterIds
Cluster ID
Enter multiple cluster IDs separated by commas(,)
namespaces
Namespace name
Enter multiple namespace names separated by commas(,)
workloadIds
Workload ID
Enter multiple workload IDs separated by commas(,)
nodeIds
Node ID
Input method (2 options)
Enter multiple node IDs separated by commas(,)
@each : Enter all IDs within the cluster
start
Start date for the query
timezone : UTC
format : yyyymmddhhmmss
end
End date for the query
timezone : UTC
format : yyyymmddhhmmss
Get the logs of Containers in the specified cluster and namespace.
Log Retrieval Method(tail or since)
The number of lines to read when the type is 'tail' (up to 10,000).
Return logs from before the value in seconds
OK
Get the per-minute trend of the memory usage for the top 5 pods in the cluster with the highest memory usage.
Start date for the query
End date for the query
OK
Get the per-minute trend of CPU usage by state (User, System, Steal, Nice, Irq, Softirq, iowait, Idle) for cluster nodes.
Start date for the query
End date for the query
OK
Get the per-minute trend of memory usage by node in the cluster, categorized by total, available, used, and used-ratio.
Start date for the query
End date for the query
OK
Get the per-minute trend of the average connection count for the Ingress Controller.
Start date for the query
End date for the query
OK
Get the per-minute trend of CPU usage for the ingress controller.
Cluster ID for the query target
Name of the Ingress Controller for the query target
Start date/time of the query (YYYYmmddHHMMss)
End date/time of the query (YYYYmmddHHMMss)
OK
Get the per-minute trend of CPU usage for the ingress controller.
Start date for the query
End date for the query
OK
Get the per-minute trend of the average request rate for the Ingress Controller.
Cluster ID for the query target
Name of the Ingress Controller for the query target
Start date/time of the query (YYYYmmddHHMMss)
End date/time of the query (YYYYmmddHHMMss)
OK
Get the per-minute trend of the average request rate for the Ingress Controller.
Start date for the query
End date for the query
OK
Get the per-minute trend of disk usage by node in the cluster, categorized by total, available, available_ratio, and used Disk.
Start date for the query
End date for the query
OK
Get the per-minute trend of the success rate (2XX) among all requests for the Ingress Controller.
Cluster ID for the query target
Name of the Ingress Controller for the query target
Start date/time of the query (YYYYmmddHHMMss)
End date/time of the query (YYYYmmddHHMMss)
OK
Get the per-minute trend of the success rate (2XX) among all requests for the Ingress Controller.
Start date for the query
End date for the query
OK