2 # The "region" parameter specifies the region in which to execute the job.
3 # If omitted, this inherits the default region name of "global".
6 # The "datacenters" parameter specifies the list of datacenters which should
7 # be considered when placing this task. This must be provided.
8 datacenters = "${datacenters}"
10 # The "type" parameter controls the type of job, which impacts the scheduler's
11 # decision on placement. This configuration is optional and defaults to
12 # "service". For a full list of job types and their differences, please see
13 # the online documentation.
15 # For more information, please see the online documentation at:
17 # https://www.nomadproject.io/docs/jobspec/schedulers
22 # The "max_parallel" parameter specifies the maximum number of updates to
23 # perform in parallel. In this case, this specifies to update a single task
27 health_check = "checks"
29 # The "min_healthy_time" parameter specifies the minimum time the allocation
30 # must be in the healthy state before it is marked as healthy and unblocks
31 # further allocations from being updated.
32 min_healthy_time = "10s"
34 # The "healthy_deadline" parameter specifies the deadline in which the
35 # allocation must be marked as healthy after which the allocation is
36 # automatically transitioned to unhealthy. Transitioning to unhealthy will
37 # fail the deployment and potentially roll back the job if "auto_revert" is
39 healthy_deadline = "3m"
41 # The "progress_deadline" parameter specifies the deadline in which an
42 # allocation must be marked as healthy. The deadline begins when the first
43 # allocation for the deployment is created and is reset whenever an allocation
44 # as part of the deployment transitions to a healthy state. If no allocation
45 # transitions to the healthy state before the progress deadline, the
46 # deployment is marked as failed.
47 progress_deadline = "10m"
50 # The "canary" parameter specifies that changes to the job that would result
51 # in destructive updates should create the specified number of canaries
52 # without stopping any previous allocations. Once the operator determines the
53 # canaries are healthy, they can be promoted which unblocks a rolling update
54 # of the remaining allocations at a rate of "max_parallel".
56 # Further, setting "canary" equal to the count of the task group allows
57 # blue/green deployments. When the job is updated, a full set of the new
58 # version is deployed and upon promotion the old version is stopped.
61 # Specifies if the job should auto-promote to the canary version when all
62 # canaries become healthy during a deployment. Defaults to false which means
63 # canaries must be manually updated with the nomad deployment promote
67 # The "auto_revert" parameter specifies if the job should auto-revert to the
68 # last stable job on deployment failure. A job is marked as stable if all the
69 # allocations as part of its deployment were marked healthy.
74 # The reschedule stanza specifies the group's rescheduling strategy. If
75 # specified at the job level, the configuration will apply to all groups
76 # within the job. If the reschedule stanza is present on both the job and the
77 # group, they are merged with the group stanza taking the highest precedence
81 delay_function = "constant"
85 # The "group" stanza defines a series of tasks that should be co-located on
86 # the same Nomad client. Any task within a group will be placed on the same
89 # For more information and examples on the "group" stanza, please see
90 # the online documentation at:
92 # https://www.nomadproject.io/docs/job-specification/group
94 group "prod-group1-${service_name}" {
95 # The "count" parameter specifies the number of the task groups that should
96 # be running under this group. This value must be non-negative and defaults
98 count = ${group_count}
100 # The restart stanza configures a tasks's behavior on task failure. Restarts
101 # happen on the client that is running the task.
103 # https://www.nomadproject.io/docs/job-specification/restart
112 # The constraint allows restricting the set of eligible nodes. Constraints
113 # may filter on attributes or client metadata.
115 # For more information and examples on the "volume" stanza, please see
116 # the online documentation at:
118 # https://www.nomadproject.io/docs/job-specification/constraint
121 attribute = "$${attr.cpu.arch}"
126 # The "task" stanza creates an individual unit of work, such as a Docker
127 # container, web application, or batch processing.
129 # For more information and examples on the "task" stanza, please see
130 # the online documentation at:
132 # https://www.nomadproject.io/docs/job-specification/task
134 task "prod-task1-${service_name}" {
135 # The "driver" parameter specifies the task driver that should be used to
139 # The "config" stanza specifies the driver configuration, which is passed
140 # directly to the driver to start the task. The details of configurations
141 # are specific to each driver, so please see specific driver
142 # documentation for more information.
145 dns_servers = [ "172.17.0.1" ]
147 "secrets/prometheus.yml:/etc/grafana/provisioning/datasources/prometheus.yml",
148 "secrets/dashboards.yml:/etc/grafana/provisioning/dashboards/dashboards.yml",
149 "secrets/grafana.ini:/etc/grafana/grafana.ini",
150 "secrets/node_exporter.json:/etc/grafana/provisioning/dashboards/node_exporter.json",
151 "secrets/docker_cadvisor.json:/etc/grafana/provisioning/dashboards/docker_cadvisor.json",
152 "secrets/nomad.json:/etc/grafana/provisioning/dashboards/nomad.json",
153 "secrets/consul.json:/etc/grafana/provisioning/dashboards/consul.json",
154 "secrets/prometheus.json:/etc/grafana/provisioning/dashboards/prometheus.json",
155 "secrets/blackbox_exporter_http.json:/etc/grafana/provisioning/dashboards/blackbox_exporter_http.json",
156 "secrets/blackbox_exporter_icmp.json:/etc/grafana/provisioning/dashboards/blackbox_exporter_icmp.json"
161 # Prometheus Node Exporter
162 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/node_exporter.json"
163 destination = "secrets/"
168 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/docker_cadvisor.json"
169 destination = "secrets/"
174 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/nomad.json"
175 destination = "secrets/"
180 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/consul.json"
181 destination = "secrets/"
186 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/prometheus.json"
187 destination = "secrets/"
191 # Prometheus Blackbox Exporter HTTP
192 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/blackbox_exporter_http.json"
193 destination = "secrets/"
197 # Prometheus Blackbox Exporter ICMP
198 source = "https://raw.githubusercontent.com/pmikus/grafana-dashboards/main/blackbox_exporter_icmp.json"
199 destination = "secrets/"
202 # The "template" stanza instructs Nomad to manage a template, such as
203 # a configuration file or script. This template can optionally pull data
204 # from Consul or Vault to populate runtime configuration data.
206 # For more information and examples on the "template" stanza, please see
207 # the online documentation at:
209 # https://www.nomadproject.io/docs/job-specification/template
213 change_signal = "SIGINT"
214 destination = "secrets/prometheus.yml"
222 url: http://prometheus.service.consul:9090
232 change_signal = "SIGINT"
233 destination = "secrets/dashboards.yml"
239 disableDeletion: false
240 updateIntervalSeconds: 10
241 allowUiUpdates: false
243 path: /etc/grafana/provisioning/dashboards
244 foldersFromFilesStructure: true
250 change_signal = "SIGINT"
251 destination = "secrets/grafana.ini"
253 app_mode = production
261 root_url = http://${service_name}.service.consul:${port}
267 admin_user = grafanauser
268 admin_password = Grafana1234
269 secret_key = SW2YcwTIb9zpOOhoPsMm
272 allow_sign_up = false
273 allow_org_create = false
274 auto_assign_org = true
275 auto_assign_org_role = Viewer
282 disable_login_form = false
283 disable_signout_menu = false
298 # The service stanza instructs Nomad to register a service with Consul.
300 # For more information and examples on the "task" stanza, please see
301 # the online documentation at:
303 # https://www.nomadproject.io/docs/job-specification/service
306 name = "${service_name}"
307 port = "${service_name}"
308 tags = [ "${service_name}$${NOMAD_ALLOC_INDEX}" ]
310 name = "Grafana Check Live"
313 tls_skip_verify = true
320 # The "resources" stanza describes the requirements a task needs to
321 # execute. Resource requirements include memory, network, cpu, and more.
322 # This ensures the task will execute on a machine that contains enough
325 # For more information and examples on the "resources" stanza, please see
326 # the online documentation at:
328 # https://www.nomadproject.io/docs/job-specification/resources
333 # The network stanza specifies the networking requirements for the task
334 # group, including the network mode and port allocations. When scheduling
335 # jobs in Nomad they are provisioned across your fleet of machines along
336 # with other jobs and services. Because you don't know in advance what host
337 # your job will be provisioned on, Nomad will provide your tasks with
338 # network configuration when they start up.
340 # For more information and examples on the "template" stanza, please see
341 # the online documentation at:
343 # https://www.nomadproject.io/docs/job-specification/network
346 port "${service_name}" {