Skip to content

cloudfoundry_dashboards job from prometheus/26.0.1

Github source: a2b84f9 or master branch

Properties

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/cloudfoundry_dashboards/ directory (learn more).

  • cf_apps_latency.json (from cf_apps_latency.json)
  • cf_apps_requests.json (from cf_apps_requests.json)
  • cf_apps_system.json (from cf_apps_system.json)
  • cf_bbs.json (from cf_bbs.json)
  • cf_cc.json (from cf_cc.json)
  • cf_cell_summary.json (from cf_cell_summary.json)
  • cf_cells_capacity.json (from cf_cells_capacity.json)
  • cf_component_metrics.json (from cf_component_metrics.json)
  • cf_component_metrics_v2.json (from cf_component_metrics_v2.json)
  • cf_diego_auctions.json (from cf_diego_auctions.json)
  • cf_diego_health.json (from cf_diego_health.json)
  • cf_doppler_server.json (from cf_doppler_server.json)
  • cf_doppler_server_v2.json (from cf_doppler_server_v2.json)
  • cf_etcd.json (from cf_etcd.json)
  • cf_etcd_operations.json (from cf_etcd_operations.json)
  • cf_garden_linux.json (from cf_garden_linux.json)
  • cf_kpis.json (from cf_kpis.json)
  • cf_lrps_tasks.json (from cf_lrps_tasks.json)
  • cf_metron_agent.json (from cf_metron_agent.json)
  • cf_metron_agent_doppler.json (from cf_metron_agent_doppler.json)
  • cf_metron_agent_v2.json (from cf_metron_agent_v2.json)
  • cf_organization_memory_quotas.json (from cf_organization_memory_quotas.json)
  • cf_organization_summary.json (from cf_organization_summary.json)
  • cf_route_emitter.json (from cf_route_emitter.json)
  • cf_router.json (from cf_router.json)
  • cf_services.json (from cf_services.json)
  • cf_space_summary.json (from cf_space_summary.json)
  • cf_summary.json (from cf_summary.json)
  • cf_uaa.json (from cf_uaa.json)
  • prometheus_cf_exporter.json (from prometheus_cf_exporter.json)
  • prometheus_firehose_exporter.json (from prometheus_firehose_exporter.json)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.

This job relies on no runtime packages.