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

NRPE dashboard not available #109

Open
peppepetra opened this issue Dec 6, 2023 · 5 comments
Open

NRPE dashboard not available #109

peppepetra opened this issue Dec 6, 2023 · 5 comments

Comments

@peppepetra
Copy link

Bug Description

When relating cos-proxy to grafana-k8s on grafana-dashboard relation, the charm goes into blocked state and the nrpe dashboard is not added to grafana

To Reproduce

  1. juju consume cos-microk8s-localhost:admin/cos.grafana-dashboards cos-grafana-dashboards
  2. juju relate cos-grafana-dashboards cos-proxy-monitors

Environment

cos-proxy rev. 52 channel edge
grafana-k8s rev. 93 channel edge

Relevant log output

$ juju status cos-proxy-monitors
...
Unit                   Workload  Agent  Machine    Public address  Ports  Message
cos-proxy-monitors/5*  blocked   idle   17/lxd/25  10.243.165.135         Missing one of (Grafana|dashboard) relation(s)
...

$ juju status --relations | grep cos-proxy-monitors
cos-proxy-monitors             n/a          blocked          1  cos-proxy                      edge      52  no       Missing one of (Grafana|dashboard) relation(s)
cos-proxy-monitors/5*              blocked      idle   17/lxd/25  10.243.165.135                                           Missing one of (Grafana|dashboard) relation(s)
cos-proxy-monitors:downstream-grafana-dashboard                      cos-grafana-dashboards:grafana-dashboard                      grafana_dashboard        regular      
cos-proxy-monitors:downstream-prometheus-scrape                      cos-scrape-interval-config-monitors:configurable-scrape-jobs  prometheus_scrape        regular      
nrpe-container:monitors                                              cos-proxy-monitors:monitors                                   monitors                 regular      
nrpe-controller:monitors                                             cos-proxy-monitors:monitors                                   monitors                 regular      
nrpe-host:monitors                                                   cos-proxy-monitors:monitors                                   monitors                 regular      
nrpe-maas-infra:monitors                                             cos-proxy-monitors:monitors                                   monitors                 regular

Additional context

No response

@lucabello
Copy link
Contributor

We should verify if this happens with the latest edge revision 58, and if so we need to investigate further :)

@przemeklal
Copy link
Member

przemeklal commented Jan 18, 2024

It seems that nrpe.json file isn't used in any way by the charm code.

It would be cool if it showed up in Grafana if:
a) cos-proxy is related to NRPE using the monitors relations
b) cos-proxy is related to COS Grafana

cc: @sed-i

@sed-i
Copy link
Contributor

sed-i commented Jan 18, 2024

The reference deployment by @przemeklal is as follows:

graph LR

subgraph openstack
nrpe-* --- cos-proxy-monitors
end

subgraph cos
prom-scrape-config --- prometheus
grafana
end

cos-proxy-monitors --- prom-scrape-config
cos-proxy-monitors --- grafana
Loading

While alert rules and metrics show up in prometheus as expected, no dashboards show up in grafana.
In fact,

  • no dashboards are present on the relation data to grafana
  • cos-proxy is instantiating GrafanaDashboardAggregator, not Provider, and afaiu, it does not read any dashboards from ./src/grafana_dashboards.

@lucabello, do you recall how your deployment looked like in #57? It seems like you were able to see the dashboard on grafana side fine.

@lucabello
Copy link
Contributor

I don't really remember, but I think the setup was the same.

@sed-i
Copy link
Contributor

sed-i commented Aug 22, 2024

@peppepetra sorry for dropping the ball on this one, but is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants