changeset 1:d5de7e857b51

Add example agent.properties file.
author Jon VanAlten <jon.vanalten@redhat.com>
date Mon, 14 Nov 2011 18:04:20 -0500
parents 7782b119c23c
children 13a5cb11acd7
files config/agent.properties
diffstat 1 files changed, 27 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/config/agent.properties	Mon Nov 14 18:04:20 2011 -0500
@@ -0,0 +1,27 @@
+## Mongo storage configuration
+# To be used when agent is running with --local argument
+mongod_port=27518
+# To be used when connecting on localhost without --local argument (cluster)
+mongos_port=27517
+### Below settings are used only by the mongo launch script
+config_port=27519
+config_uri=localhost
+#
+## Backend Configuration
+# This must be a comma separated list naming each backend that should run
+backends=
+# For each backend specified above, there must be a .active property specified.
+# ie: for backend 'foo' there should be a 'foo.active = bar' line.  'bar'
+# should be a comma separated list including one or more of:
+#   'new' - The backend should attempt to attach to any new java process that
+#           starts.  Existing processes should not be instrumented.
+#   'all' - The backend should attempt to attach to all existing java
+#           java processes currently running on the machine.
+#   '[lvmid]' - One or more Local Virtual Machine IDs may be specified.  These
+#           are equivalent to the Linux process id.  This allows for the case
+#           of specific existing java processes to be instrumented.
+#
+# Backends may also use their name as prefix for backend-specific configuration.
+# For example, if backend foo requires a property called bar, then a line
+# containing 'foo.bar=baz' should be included.
+