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
The response may include the success of the requested task, data, error messages, etc
Below is an example of a simple JSON-formatted API response.
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
You can determine the success of the task based on the 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
The API REFERENCE document below contains only the content regarding the "result" value in case of successful task execution.
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!
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.
Get detailed information for the Secret in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/secrets/{secretName}
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 detailed information for the exposed service in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/services/{serviceName}
Get detailed information for CronJob in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/cronjobs/{cronJobName}
Get detailed information for Deployment in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/deployments/{deploymentName}
Get the logs of Containers in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/pods/{podName}/containers/log
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
Get detailed information for the workloads in the specified workspace and service map.
/v1/workspaces/{workspaceSeq}/servicemaps/{servicemapSeq}/workloads/{workloadName}
Get the total CPU usage per minute of the cluster.
/v1/monitoring-clusters/metric/cpu/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the memory usage for the top 5 pods in the cluster with the highest memory usage.
/v1/monitoring-clusters/metric/pod-memory-top/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the number of pods by status (Unknown, Failed, Pending, Running, Succeeded).
/v1/monitoring-clusters/metric/pod-running/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the CPU usage for the top 5 pods in the cluster with the highest CPU usage.
/v1/monitoring-clusters/metric/pod-cpu-top/result/transition
Start date for the query
End date for the query
Get detailed information for the ConfigMap in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/configmaps/{configmapName}
Get the per-minute trend of CPU load by node in the cluster.
/v1/monitoring-nodes/metric/load/result/transition
Start date for the query
End date for the query
Get the per-minute trend of CPU usage by node in the cluster.
/v1/monitoring-nodes/metric/cpu-usage/result/transition
Start date for the query
End date for the query
Get detailed information for DaemonSet in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/daemonsets/{daemonSetName}
Get detailed information for the Ingress in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/ingresses/{ingressName}
Get detailed information for PVC in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/persistentvolumeclaims/{pvcName}
Get detailed information for StatefulSet in the specified cluster and namespace.
/v1/clusters/{clusterId}/namespaces/{namespaceName}/statefulsets/{statefulSetName}
Get the per-minute trend of the overall memory usage in the cluster, categorized by cache and working set.
/v1/monitoring-clusters/metric/memory/result/transition
Start date for the query
End date for the query
Get the per-minute trend of overall CPU and memory requests/limits in the cluster.
/v1/monitoring-clusters/metric/quota/result/transition
Start date for the query
End date for the query
Get the uptime of cluster nodes. The operation time represents the duration (without restarting) after the booting of the node (server).
/v1/monitoring-nodes/metric/uptime/result/current
Get the number of requests to the Kubernetes API server in the past 2 minutes, converted to requests per second.
/v1/monitoring-clusters/metric/kube-api-server-request/result/transition
Start date for the query
End date for the query
Get the list of pods restarted in the cluster.
/v1/monitoring-clusters/metric/pod-restart-list/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the overall network usage in the cluster, categorized by inbound and outbound.
/v1/monitoring-clusters/metric/network/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the average connection count for the Ingress Controller.
/v1/monitoring-ingress/metric/controller-connections/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the average request rate for the Ingress Controller.
/v2/monitoring-ingress/metric/controller-requests/result/transition
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)
Get the per-minute trend of the average request rate for the Ingress Controller.
/v1/monitoring-ingress/metric/controller-requests/result/transition
Start date for the query
End date for the query
Get the per-minute trend of the success rate (2XX) among all requests for the Ingress Controller.
/v2/monitoring-ingress/metric/controller-success-rate/result/current
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)
Get the per-minute trend of the success rate (2XX) among all requests for the Ingress Controller.
/v1/monitoring-ingress/metric/controller-success-rate/result/transition
Start date for the query
End date for the query
Get the per-minute trend of memory usage by node in the cluster, categorized by total, available, used, and used-ratio.
/v1/monitoring-nodes/metric/memory-usage/result/transition
Start date for the query
End date for the query
Get the per-minute trend of disk usage by node in the cluster, categorized by total, available, available_ratio, and used Disk.
/v1/monitoring-nodes/metric/disk-usage/result/transition
Start date for the query
End date for the query
Get the per-minute trend of CPU usage by state (User, System, Steal, Nice, Irq, Softirq, iowait, Idle) for cluster nodes.
/v1/monitoring-nodes/metric/cpu-usage-by-mode/result/transition
Start date for the query
End date for the query
Get the per-minute trend of disk I/O speed change rate by node in the cluster.
/v1/monitoring-nodes/metric/disk-io/result/transition
Start date for the query
End date for the query
Get the per-minute trend of CPU usage for the ingress controller.
/v2/monitoring-ingress/metric/controller-average-cpu-usage/result/transition
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)
Get the per-minute trend of CPU usage for the ingress controller.
/v1/monitoring-ingress/metric/controller-average-cpu-usage/result/transition
Start date for the query
End date for the query
Get the per-minute trend of network usage by device for cluster nodes.
/v1/monitoring-nodes/metric/traffic-by-device/result/transition
Start date for the query
End date for the query