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

COS / Dashboard "MongoDB ReplSet Summary" has empty data on CPU section #512

Open
gustavosr98 opened this issue Nov 7, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@gustavosr98
Copy link

Steps to reproduce

Follow this guide
https://charmhub.io/mongodb/docs/h-view-metrics

Expected behavior

All plots to show data

Actual behavior

Screenshot 2024-11-07 at 18 01 15

Versions

All versions can be seen in Juju status

# (base) blue@blue:~$ juju status
Model  Controller  Cloud/Region         Version  SLA          Timestamp
mongo  lxd         localhost/localhost  3.5.4    unsupported  23:03:15Z

SAAS                             Status  Store  URL
alertmanager-karma-dashboard     active  lxd    admin/cos.alertmanager-karma-dashboard
grafana-dashboards               active  lxd    admin/cos.grafana-dashboards
loki-logging                     active  lxd    admin/cos.loki-logging
prometheus-receive-remote-write  active  lxd    admin/cos.prometheus-receive-remote-write

App                       Version  Status  Scale  Charm                     Channel        Rev  Exposed  Message
data-integrator                    active      1  data-integrator           latest/stable   41  no
grafana-agent                      active      3  grafana-agent             latest/edge    299  no       tracing: off
mongodb                            active      3  mongodb                   6/stable       199  no
self-signed-certificates           active      1  self-signed-certificates  latest/stable  155  no

Unit                         Workload  Agent  Machine  Public address  Ports      Message
data-integrator/0*           active    idle   0        10.58.159.57
mongodb/0                    active    idle   0        10.58.159.57    27017/tcp
  grafana-agent/1            active    idle            10.58.159.57               tracing: off
mongodb/1*                   active    idle   1        10.58.159.81    27017/tcp  Primary
  grafana-agent/0*           active    idle            10.58.159.81               tracing: off
mongodb/2                    active    idle   2        10.58.159.224   27017/tcp
  grafana-agent/2            active    idle            10.58.159.224              tracing: off
self-signed-certificates/0*  active    idle   0        10.58.159.57

Machine  State    Address        Inst id        Base          AZ  Message
0        started  10.58.159.57   juju-dae5f5-0  [email protected]      Running
1        started  10.58.159.81   juju-dae5f5-1  [email protected]      Running
2        started  10.58.159.224  juju-dae5f5-2  [email protected]      Running
@gustavosr98 gustavosr98 added the bug Something isn't working label Nov 7, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5922.

This message was autogenerated

@MiaAltieri
Copy link
Contributor

@gustavosr98 Bravo! Thanks for the feedback!

The metrics in these dashboards are metrics exposed via the node exporter which lives inside grafana-agent . To see them select Grafana Agent from the applications (image one)

To view CPU usage then scroll back to the dashbord (image two)

Right now I am talking to ob11y to see if we can configure grafana agent and MongoDB so that the dashboard can be populated automatically

Screenshot 2024-12-06 at 17 05 55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants