Frequently asked questions (FAQ)¶
This section outlines the most frequently asked questions (FAQs) about Percona Everest.
What is DatabaseEngine?¶
The DatabaseEngine is a resource that defines the compatible PG/PXC/MongoDB versions for the current Percona Everest version.
You can use this resource to query and update the list of supported engine versions.
Refer to our API documentation for usage information.
Do we have logs of the API calls made?¶
Yes, the Percona Everest backend has logs. It runs as a percona-everest deployment within the everest-systemnamespace.
-
Accessing these logs help us verify whether an API call was initiated for a specific user operation.
-
Identify any errors that may have occurred during that process.
Note
Percona Everest logs are crucial for troubleshooting issues where an operation is completed, but the corresponding Everest operator resource hasn’t been created for some reason.
Where are Percona Everest backend logs stored?¶
You can retrieve the logs from the pods associated with this deployment.
To access them, run:
kubectl logs -f deploy/percona-everest -n everest-system
How to troubleshoot issues between the UI and the Percona Everest API?¶
You can view these logs in the console of your web browser.
Should we troubleshoot resources that are not part of the Percona Everest operator image?¶
All communication with Everest resources begins with the API.
The API is responsible for updating Everest resources, while the Everest operator continues to create resources for the corresponding database operators.
Troubleshooting flow
When debugging, start with the API, then proceed to the Everest operator, and finally examine the individual database operators.
Does Percona Everest deploy PMM servers?¶
Percona Everest doesn’t deploy PMM (Percona Monitoring and Management).
Instead, we configure PMM agents in each DB deployment to communicate with an existing PMM server.
The important points are:
-
The
MonitorConfigresource in Percona Everest manages PMM agent setup. -
An API key is generated to facilitate data transmission. This API key allows us to configure monitoring endpoints for individual database operators, enabling them to send data to PMM.
Note
PMM is an external service we support and does not necessarily fit into our architecture.
Get expert help¶
If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.