Skip to content

health_monitor job from bosh/144

Github source: 4f117dc0 or master branch

Properties

aws

access_key_id

AWS access key id

secret_access_key

AWS secret access key

director

address

Address of the Bosh Director to connect to

port

Port of the Bosh Director to connect to

Default
25555

event_nats

address

Address of the event NATS message bus to connect to

password

Password for event NATS message bus connection

port

Port of the event NATS message bus port to connect to

user

User for the event NATS message bus connection

event_nats_enabled

Enable event NATS message bus plugin

Default
false

hm

cloud_watch_enabled

Enable AWS CloudWatch Plugin

Default
false

datadog

api_key

API Key for DataDog

application_key

Health Monitor Application Key for DataDog

pagerduty_service_name

Service name to alert in PagerDuty upon HM events

datadog_enabled

Enable DataDog plugin

Default
false

director_account

password

Password to access Bosh Director

user

User to access Bosh Director

email_interval

Interval (in seconds) to deliver alerts by email (optional)

email_notifications

Enable email notifications plugin

Default
false

email_recipients

Email of recipients (Array)

graphite

address

Graphite address

port

Graphite port

prefix

Prefix that will be added to all metrics sent to Graphite

graphite_enabled

Enable Graphite plugin

Default
false

http

password

Password clients must use to access Health Monitor via HTTP Basic Auth

port

TCP port Health Monitor daemon listens on

Default
25923
user

Username clients must use to access Health Monitor via HTTP Basic Auth

intervals

agent_timeout

Interval (in seconds) to consider an agent has timed out

Default
60
analyze_agents

Interval (in seconds) to analyze the status of agents

Default
60
log_stats

Interval (in seconds) to log Health Monitor statistics

Default
60
poll_director

Interval (in seconds) to get the list of managed VMs from Bosh Director

Default
60
poll_grace_period

Interval (in seconds) between discovering managed VMs and analyzing their status

Default
30
prune_events

Interval (in seconds) to prune received events

Default
30
rogue_agent_alert

Interval (in seconds) to consider an agent as rogue (an agent that is no part of any deployment)

Default
120

loglevel

Level of log messages (fatal, error, warn, info, debug)

Default
info

pagerduty

http_proxy

HTTP proxy to connect to PagerDuty (optional)

service_key

PagerDuty service API key

pagerduty_enabled

Enable PagerDuty plugin

Default
false

resurrector

minimum_down_jobs

If the total number of down jobs in a deployment is below this threshold, the resurrector will always request a down job be recreated

Default
5
percent_threshold

Percentage of total jobs in a deployment that must be down for the resurrector to to stop sending recreate-job requests. Used in ‘meltdown’ situations so resurrector will not try to recreate the world.

Default
0.2
time_threshold

Time (in seconds) for which an alert in the resurrector is considered ‘current’; alerts older than this are ignored when deciding to recreate a job.

Default
600

resurrector_enabled

Enable VM resurrector plugin

Default
false

smtp

auth

SMTP Authentication type (optional, only “plain” is supported)

domain

SMTP EHLO domain

from

Email of sender

host

Address of the SMTP server to connect to

password

Password for SMTP Authentication (optional, use in conjuction with hm.smtp.auth)

port

Port of the SMTP server to connect to

tls

Use STARTTLS (optional)

user

User for SMTP Authentication (optional, use in conjuction with hm.smtp.auth)

tsdb

address

Address of TSDB to connect to

port

Port of TSDB to connect to

tsdb_enabled

Enable TSDB plugin

Default
false

varz_enabled

Enable varz plugin

Default
false

nats

address

Address of the NATS message bus to connect to

password

Password for NATS message bus connection

port

Port of the NATS message bus port to connect to

Default
4222

user

User for the NATS message bus connection

Templates

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

  • bin/health_monitor_ctl (from health_monitor_ctl)
  • config/health_monitor.yml (from health_monitor.yml.erb)

Packages

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