Skip to content

Add pre-defined environment variables to task definition.#451

Merged
ejholmes merged 3 commits intomasterfrom
add-empire-env
May 26, 2015
Merged

Add pre-defined environment variables to task definition.#451
ejholmes merged 3 commits intomasterfrom
add-empire-env

Conversation

@ejholmes
Copy link
Copy Markdown
Contributor

This would be a temporary workaround for the lack of support for labels in ECS. If we merge this, then we can change the SYSLOG_STRUCTURED_DATA environment variable in logspout to extract these specific variables into the structured-data fields in log messages. EZPZ log filtering for app name, version and process type.

Soon the ecs agent will add the task arn, container-name, family and version as well. Once ECS supports adding labels to task definitions, then we can move these to labels like com.remind.empire.appname, com.remind.empire.process, com.remind.empire.release.

Related to #445

@phobologic
Copy link
Copy Markdown
Contributor

👍

@ejholmes
Copy link
Copy Markdown
Contributor Author

gliderlabs/logspout#100 kinda blocks this for now. Might just fork logspout.

ejholmes added a commit that referenced this pull request May 26, 2015
Add pre-defined environment variables to task definition.
@ejholmes ejholmes merged commit 95fe13c into master May 26, 2015
@ejholmes ejholmes deleted the add-empire-env branch May 26, 2015 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants