Frequently asked questions (FAQ)¶

This section outlines the most frequently asked questions (FAQs) about Percona Everest.

What is DatabaseEngine?¶

Provide an example of Database Engine Operations. Does it manage database operators, such as upgrades, or is it related to Percona Everest resources?

Answer: The DatabaseEngine is a resource that contains compatible PG/PXC/MongoDB versions for the current Everest version. This information can be retrieved and updated.

Refer to our API documentation for in-depth information.

Do we have logs of the API calls made?¶

This will help us validate whether an API call was made for a user operation and whether any errors occurred during the process.

Answer: Yes, the Everest backend has logs. It runs as a percona-everest deployment within the everest-systemnamespace.

Note

This is crucial for troubleshooting issues where an operation is completed, but the corresponding Everest operator resource hasn’t been created for some reason.
- If we have these logs, where are they stored?
Answer: You can retrieve logs from the pods associated with this deployment.

Do we have any logs for frontend actions, to troubleshoot issues between the front end and the Percona Everest API?¶

Answer: The logs will be accessible in the console of the web browser.

Is there a resource that manages the API calls and interacts with the individual resources?¶

Should we check the logs for troubleshooting when issues arise? Alternatively, does the Everest API communicate directly with the Everest operator resources?
If so, should we correlate the Percona operator issue with the corresponding Everest resource and address the problem from that point?

Answer: 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. 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?¶

While MonitorConfig is present, does this resource interact directly with each pmm-agent container on the database pods, deploy new PMM Servers, and modify their configuration?

Answer:

Percona Everest doesn’t deploy PMM. Instead, we configure PMM agents in each DB deployment to communicate with an existing PMM server.

When communicating with PMM, we generate an API key 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.

Community Forum Get a Percona Expert