CRS Configuration Options

Usage Example

 
java -XX:AzCRSMode=on -jar MyApp.jar

Applying Tags

Tag keys must begin with a letter. Both key and value may contain lower and upper case letters, and numbers. These additional characters are also allowed:

 
ALLOWED_KEY_EXTRA_CHARS = "-_."
ALLOWED_VALUE_EXTRA_CHARS = "-_. :/@" <-- Includes space

Special Tags

This tag is handled in a specific way with the system:

How to Use Tags

Tags can be specified with a command line argument or environment variable:

 
# With command line option
-Dcom.azul.crs.instance.tags="system-prop.tag_1=system prop/value@1; system_prop_tag.2=system prop:value/2"

# With environment variable
export CRS_TAGS="env.tag-1=value:1; env_Tag_2=value 2"

For example, using the command line option:

 
java -XX:AzCRSMode=on \
    -XX:AzCRSArguments=api.url={forwarder_endpoint} \
    -Dcom.azul.crs.instance.tags="AppEnv=MyApplicationTag" \
    -jar MyApp.jar

Recommended Tagging Practice

It is important that you properly tag your instances. As a general rule, tagging should reflect the way you categorize your Java applications. For example, you can use "west-coast", "east-coast", and so on to distinguish between different availability zones/locations.

Usage Examples

 
# Environment variable for Azul Intelligence Cloud Agent
export JDK_JAVA_OPTIONS="-javaagent:${AGENTDIR}/ic-agent.jar=expression1,expression2,expression3 \
  -DaagentDir=${AGENTDIR} \
  -Djava.security.policy=${AGENTDIR}/agent.all.policy"

# Command line option for Azul JDK or JRE
java -XX:AzCRSArguments=expression1,expression2,expression3 -jar MyApp.jar

# Environment variable for Azul JDK or JRE
export AZ_CRS_ARGUMENTS=expression1,expression2,expression3

Azul Intelligence Cloud Agent

For the Azul Intelligence Cloud Agent, both Tags and Arguments are is configured with environment variables. Tags are defined with CRS_TAGS, while arguments are added in the agent configuration with JDK_JAVA_OPTIONS.

 
export CRS_TAGS=YOUR_CRS_TAGS
export JDK_JAVA_OPTIONS="-javaagent:${AGENTDIR}/ic-agent.jar=YOUR_CRS_ARGUMENTS \
  -DaagentDir=${AGENTDIR} \
  -Djava.security.policy=${AGENTDIR}/agent.all.policy"

For example:

 
export CRS_TAGS="env.tag-1=value:1; env_Tag_2=value 2"
export JDK_JAVA_OPTIONS="-javaagent:${AGENTDIR}/ic-agent.jar=sendPOMData=false,log=info \
  -DaagentDir=${AGENTDIR} \
  -Djava.security.policy=${AGENTDIR}/agent.all.policy"

Azul JDK or JRE Runtime

To enable and configure your instances running with an Azul runtime and CRS, you can choose to use one of these three options:

The connected runtime looks for the configuration parameters in the order described above. You can use a combination of these options. If you set a parameter in several ways, for example via both the environment variable and configuration file, the JVM uses the value that comes first in the order given above.

In addition, the Forwarder address can be configured via DNS records. See Service discovery via DNS.

 
java -XX:AzCRSMode=on \
    -XX:AzCRSArguments=api.url={forwarder_endpoint} \
    MyApp

 
java -XX:AzCRSMode=on \
    -XX:AzCRSArguments=api.url={forwarder_endpoint},log=debug,delayTermination=120000,delayInitiation=0 \
    -Dcom.azul.crs.instance.tags={tags} \
    MyApp

 
export CRS_TAGS={tags}
export AZ_CRS_ARGUMENTS=enable,api.url={forwarder_endpoint},log=debug,delayTermination=120000,delayInitiation=0
java MyApp