Trouble shooting section for Percona Everest #157
Conversation
|
Your Render PR Server URL is https://everest-doc-pr-157.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-cr23q0rtq21c739c4p3g. |
rasika-chivate
temporarily deployed
to
trouble_shooting+everest - Everest Release Branch PR #157
Render
Destroyed
| - Everest | ||
| - VictoriaMetrics |
There was a problem hiding this comment.
Mayank is working on a change right now that will remove the Everest and VM operators from OLM. Since we are working on this right now we might as well prepare for the 1.4 release and remove them from this OLM section.
We should still mention somewhere that we install the everest operator in the everest-system namespace and the VM operator in the everest-monitoring namespace.
docs/reference/faq.md
Outdated
| **Answer:** | ||
| The logs will be accessible in the console of the web browser. | ||
|
|
||
| ### Are there any additional resources that are not included in the image? |
There was a problem hiding this comment.
I don't find this title very descriptive. It seems to me that the questions you ask below are unrelated with this 🤔
There was a problem hiding this comment.
@recharte Rephrased it:
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?
| While `MonitorConfig` is present, does this resource interact directly with each `ppm-agent` container on the database pods, deploy new PMM Servers, and modify their configuration? | ||
|
|
||
| **Answer:** | ||
| 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. |
There was a problem hiding this comment.
I feel that you asked an important the correct question (deploy new PMM Servers, and modify their configuration?) but don't answer it properly.
I think we should explicitly mention that everest doesn't deploy PMM. Instead, we configure PMM agents in each DB deployment to communicate with an existing PMM server.
docs/reference/faq.md
Outdated
| 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. | ||
|
|
||
|
|
||
| ### Why PMM appears to be absent in this context? |
There was a problem hiding this comment.
I don't find this title very descriptive 🤔
Co-authored-by: Diogo Recharte <[email protected]>
…/everest-doc into trouble_shooting+everest
Co-authored-by: Diogo Recharte <[email protected]>
it-percona
temporarily deployed
to
trouble_shooting+everest - everest-doc PR #157
Render
Destroyed
Co-authored-by: Diogo Recharte <[email protected]>
rasika-chivate
temporarily deployed
to
trouble_shooting+everest - Everest Release Branch PR #157
Render
Destroyed
it-percona
temporarily deployed
to
trouble_shooting+everest - everest-doc PR #157
Render
Destroyed
rasika-chivate
temporarily deployed
to
trouble_shooting+everest - Everest Release Branch PR #157
Render
Destroyed
Co-authored-by: Diogo Recharte <[email protected]>
Add a trouble shooting section for Percona Everest