Improvement Request: DaGPusher

[blebail]

Hi Luigi,

Is there any plans to customize the tag criteria sent through DaGPusher? If you have two DagPusher from two different miners, it is complex to figure out which one is coming from one DaGPusher and which one is coming from another.

Thanks

Regards,

[lmori · Accepted solution]

Hi Bertrand,

good point ! it is possible today, but you have to create a new prototype for it:

- create a new file .yml in /opt/minemeld/local/prototypes

- content should be (double check the whitespaces):

description: test dagpusher
prototypes: 
   dagPusher:
        development_status: EXPERIMENTAL
        node_type: output
        description: >
            new dag pusher prototype with prefix newprefix_
        class: minemeld.ft.dag.DagPusher
        config:
            tag_prefix: newprefix_

- reload the UI and you should find the new prototype

- the new prototype will generate dag tags with prefix newprefix_

(Yes, there is an ER already for creating prototypes from the UI :-))

Thanks !

luigi 

[lmori · Accepted solution]

Hi Bertrand,

good point ! it is possible today, but you have to create a new prototype for it:

- create a new file .yml in /opt/minemeld/local/prototypes

- content should be (double check the whitespaces):

description: test dagpusher
prototypes: 
   dagPusher:
        development_status: EXPERIMENTAL
        node_type: output
        description: >
            new dag pusher prototype with prefix newprefix_
        class: minemeld.ft.dag.DagPusher
        config:
            tag_prefix: newprefix_

- reload the UI and you should find the new prototype

- the new prototype will generate dag tags with prefix newprefix_

(Yes, there is an ER already for creating prototypes from the UI :-))

Thanks !

luigi 

[blebail]

Luigi,

You mean newprefix_, right?

Thanks

B.

[lmori]

Yes, fixed. Thanks