Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ng-monitoring can't scrape CPU profile #251

Open
giant-panda666 opened this issue Jul 3, 2024 · 0 comments
Open

ng-monitoring can't scrape CPU profile #251

giant-panda666 opened this issue Jul 3, 2024 · 0 comments

Comments

@giant-panda666
Copy link

  1. At first, ng-monitoring is deployed in namespace A. And then, the continuous profiling is enabled on tidb dashboard.
  2. i want ng-monitoring and tidb dashboard to deployed in namespace B. So i deleted the tidbNGMonitoring and tidbDashboard. After change the namespace of them to namespace B, i apply them to k8s.
  3. After tidb dashboard and ng-monitoring is running, i enable the continuous profiling on tidb dashboard. but some failed occured:
    image
    image
  4. what i see in tikv logs is: "Already in CPU Profiling". So is it the ng-monitoring make tikv in CPU Profiling before i delete, and make ng-monitoring can't scrape after recreated?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant