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

Control Plane Monitor of Child CF Deployments #3

Open
r0bm3 opened this issue Aug 13, 2018 · 1 comment
Open

Control Plane Monitor of Child CF Deployments #3

r0bm3 opened this issue Aug 13, 2018 · 1 comment
Labels
TYPE: Documentation Documentation incorrect or missing

Comments

@r0bm3
Copy link

r0bm3 commented Aug 13, 2018

Currently, the genesis kit assumes when selecting "monitor CF installation" that CF will be installed inside of the control plane.

As a user of Prometheus within the genesis control plane, I need the ability to monitor child genesis CF deployments from the control plane.

below is the output of the preflight check that outlined the issue when attempting this configuration:

$ genesis deploy smo-control-plane.yml
Checking availability of the 'smo-control-plane' BOSH director...
Preparing to deploy smo-control-plane to 'smo-control-plane' BOSH director.

  • Fetching cloud config from 'smo-control-plane'
    Downloading cloud config from 'smo-control-plane' BOSH director...
  • Running preflight checks against [smo-control-plane]:
    [smo-control-plane] running cloud-config and environmental parameter checks...
    cloud-config [OK]
    ✔ secret/smo/control/plane/prometheus/nginx/ssl_certificate [OK]
    environment files [OK]
    [smo-control-plane] running manifest viability checks...
    5 error(s) detected:
  • $.instance_groups.prometheus.jobs.bosh_exporter.properties.bosh_exporter.bosh.uaa.client_secret: secret secret/smo/control/plane/bosh/uaa/clients/prometheus:secret not found
  • $.instance_groups.prometheus.jobs.cf_exporter.properties.cf_exporter.cf.api_url: secret secret/exodus/smo-control-plane/cf:api_url not found
  • $.meta.cf_firehose_uaa_vault: secret secret/exodus/smo-control-plane/cf:vaulted_uaa_clients not found
  • $.meta.cf_system_domain: secret secret/exodus/smo-control-plane/cf:system_domain not found
  • $.meta.uaa_client_secret: failed to retrieve (( vault "secret/exodus/" meta.bosh_exodus_path "/cf from Vault (https://10.222.96.163): no handler for route '(( vault "secret/exodus/" meta.bosh_exodus_path "/cf'

Unable to merge smo-control-plane manifest (run failed):

@jhunt
Copy link
Contributor

jhunt commented Aug 16, 2018

If you want to monitor CF, you have to spin a separate prometheus instance per CF. Due to the nature of the prometheus-boshrelease, you cannot co-mingle CFs in one prometheus.

For that reason, the Genesis Kit pretty much expects to find the CF in the same environment as the BOSH director that is deploying the Prometheus, which is not the case in with the Operations Tier / Control Plane.

@dennisjbell dennisjbell added the TYPE: Documentation Documentation incorrect or missing label Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TYPE: Documentation Documentation incorrect or missing
Projects
None yet
Development

No branches or pull requests

3 participants