Kubernetes events provide insight into what is happening inside a cluster, based on which KubeSphere adds longer historical query and aggregation capabilities, and also supports event query for tenant isolation.
This guide demonstrates how you can do multi-level, fine-grained event queries to track the status of your components.
KubeSphere Events needs to be enabled.
The event query function is available for all users. Log in to the console with any account, hover over in the lower-right corner and select Event Search.
In the displayed dialog box, you can view the number of events that the account has permission to view.
KubeSphere supports event queries on each cluster separately if you have enabled the multi-cluster feature. You can click on the left of the search box and select a target cluster.
KubeSphere stores events for last seven days by default.
You can click the search box and enter a condition to search for events by message, workspace, project, resource type, resource name, reason, category, or time range (for example, use
Time Range:Last 10 minutesto search for events within the last 10 minutes).
Click any one of the results from the list, and you can see raw information of it. It is convenient for developers in terms of debugging and analyzing.
NoteThe event query interface supports dynamic refreshing every 5s, 10s or 15s.
Was this page Helpful?
Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.