Hi there John
Thanks for the clarification. My initial aim was, exactly, to expose those
parameters that, as you say, some people don't think should be exposed.
My use case is to allow jobs with different native parameters to be
scheduled on our clouster from our Galaxy server. Perhaps a better a
So job metrics are completely different than what you described here.
Job metrics are enabled by default and can be configured fairly
directly by modifying config/job_metrics_conf.xml. New plugins are
relatively easy to write and can be added as python files to
lib/galaxy/jobs/metrics/instrumenters
Hi there
I'm trying to understand how the job metrics configuration works. Reading
through various examples, it looks like it works together with the dynamic
destination support.
First on the dynamic destination support, this works, as I understand it,
by importing modules (files ending in .py) f
