Skip to content

Allow setting of DynaTrace agent name via environment variable#235

Closed
tom-collings wants to merge 3 commits intocloudfoundry:masterfrom
tom-collings:master
Closed

Allow setting of DynaTrace agent name via environment variable#235
tom-collings wants to merge 3 commits intocloudfoundry:masterfrom
tom-collings:master

Conversation

@tom-collings
Copy link

A customer has asked for a non-default (that is, something different than the application name) to be used for the DynaTrace agent name. By setting an environment variable, we can allow end users to set the agent name.

The environment variable is JBP_CONFIG_DYNATRACE_AGENT_NAME. If it exists, the value of this environment variable will be used for the DynaTrace agent name in the JVM Options. If it does not exist, the default behaviour (using the application name) will be used.

This is my first foray into ruby. I used other ruby files in the buildpack as a general style guide, any feedback will be greatly appreciated.

Also, its unclear how to sign the CLA. Should I be receiving some notification with instructions?

tom-collings and others added 3 commits September 30, 2015 12:03
…a the

environment variable JBP_CONFIG_DYNATRACE_AGENT_NAME.  If this environment
variable exists, the value wull be used for the agent name.  If the value
does not exist, then the default value (application name) will be used.
Allow the configuration of a DynaTrace agent name by setting the
JBP_CONFIG_DYNATRACE_AGENT_NAME environment variable.  If the environment
variable exists, use that value.  If it does not, use the default
behaviour, which is the application name.

Issue #234
@cfdreddbot
Copy link

Hey tom-collings!

Thanks for submitting this pull request!

All pull request authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate).

When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization.

If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions.

@nebhale
Copy link
Contributor

nebhale commented Oct 2, 2015

Completed in 6e53039

@nebhale nebhale closed this Oct 2, 2015
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.

3 participants