Allow setting a 'typeName' inside a YAML query definition
Allow setting a 'typeName' inside a YAML query definition

Certain mbean objectnames do not have a 'name' key property used to uniquely
identify a particular group of metrics when using a wildcard query.

This adds support for an optional 'typeName' attribute to be defined in a query
section (defaulting to 'name', to replicate previous behaviour), the value of
which propagates to the outputWriters section in the JSON output.

Example YAML definition:
queries:
    - name: activemq
      obj : "org.apache.activemq:BrokerName=embedded,Type=Queue,Destination=*"
      typeName: "Destination"
      resultAlias: "activemq"
      attr:
        - "QueueSize"

magullo/jmxtrans,peterwoj/jmxtrans,kevinconaway/jmxtrans,RTBHOUSE/jmxtrans,kulcsartibor/jmxtrans,kulcsartibor/jmxtrans,RTBHOUSE/jmxtrans,Shopify/jmxtrans,magullo/jmxtrans,Stackdriver/jmxtrans,peterwoj/jmxtrans,kevinconaway/jmxtrans,RTBHOUSE/jmxtrans,derjust/jmxtrans,allenbhuiyan/jmxtrans,jmxtrans/jmxtrans,jmxtrans/jmxtrans,peterwoj/jmxtrans,magullo/jmxtrans,yogoloth/jmxtrans,jmxtrans/jmxtrans,jmxtrans/jmxtrans,allenbhuiyan/jmxtrans,peterwoj/jmxtrans,allenbhuiyan/jmxtrans,derjust/jmxtrans,Stackdriver/jmxtrans,airbnb/jmxtrans,yogoloth/jmxtrans,magullo/jmxtrans,kulcsartibor/jmxtrans,jmxtrans/jmxtrans,yogoloth/jmxtrans,kevinconaway/jmxtrans,derjust/jmxtrans,yogoloth/jmxtrans,airbnb/jmxtrans,allenbhuiyan/jmxtrans,kulcsartibor/jmxtrans,derjust/jmxtrans,RTBHOUSE/jmxtrans,Shopify/jmxtrans,kevinconaway/jmxtrans