Reorder User Data #124
Merged
Reorder User Data #124
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, Fluentd and Prometheus/whatever time series DB can potentially be run on Nomad. If the Nomad cluster is unhealthy or the jobs are not running properly, new nodes will never be able to bootstrap properly. We rearrange the order of launching so that these nodes can still bootstrap their respective services. On the downside, this means that we might not even know that the nodes are not sending their logs. Perhaps #44 will help?
guangie88
approved these changes
Aug 2, 2018
lawliet89
added a commit
that referenced
this pull request
Aug 3, 2018
* Configure Telemetry for Consul via a new script * Configure Nomad telemetry in Nomad configuration * Procstat log Also rearrange startup sequence * Add for Vault and re-order user_data sequence * Simplify Telegraf configuration * Move telegraf and td-agent to the back Replicates #124 * Update README * Fix incorrect paths * Rework Telegraf configuration * Differentiate between consul server and agents * Format Terraform * Update README * Add note about consul-template * Update path * Rename variable to `telegraf_enabled` * Add missing flag * Render all known nodes for ES * Remove telegraf conf from Packer template * Fix script errors * Fix typo
qbiqing
pushed a commit
that referenced
this pull request
Mar 10, 2020
* Add statsd and update to consul hcl config * Update to use inline config * Update AMI with working inline config * Update submodule * Update submodule * Use back the correct module commit * Update again * Update vendor to the right stuff * Add td-agent module as part of core * Fix previous mistake in td-agent.conf for Vault * Fix another bug with td-agent-vars for Vault * Update AMI with td-agent core integrataion * Update vendor * Update to use vendor commit on master
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Fluentd and Prometheus/whatever time series DB can
potentially be run on Nomad. If the Nomad cluster is unhealthy
or the jobs are not running properly, new nodes will never be
able to bootstrap properly. We rearrange the order of launching
so that these nodes can still bootstrap their respective services.
On the downside, this means that we might not even know that the nodes
are not sending their logs.
Perhaps #44 will help?