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_relation_joined should ensure the vector binary is present #59

Open
lucabello opened this issue Apr 5, 2023 · 0 comments
Open

Comments

@lucabello
Copy link
Contributor

lucabello commented Apr 5, 2023

Bug Description

The relation between cos-proxy and nrpe is not sufficient for logs to reach Loki when related to it cross-model. The reason for this is that vector doesn't start when the nrpe relation is joined. Adding filebeat to the model makes vector start successfully.

To address this bug, modify _nrpe_relation_joined() so that it ensures the vector binary is there, the same way it's done for _filebeat_relation_joined().

To Reproduce

machine model

  1. juju deploy ubuntu
  2. juju deploy nrpe
  3. juju deploy cos-proxy
  4. juju relate nrpe ubuntu
  5. juju relate cos-proxy nrpe

k8s model

  1. juju deploy cos-lite --channel=edge
  2. cross-model relate cos-proxy to loki

Environment

∮ microk8s version
MicroK8s v1.26.1 revision 4596
∮ juju --version
3.1.0-genericlinux-amd64
∮ lxd --version
5.12

Relevant log output

-

Additional context

No response

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

1 participant