[GitHub] activemq-artemis issue #1506: ARTEMIS-1384 adding CLI command (qstat) to dis...

2017-09-05 Thread pgfox 
Github user pgfox commented on the issue:

https://github.com/apache/activemq-artemis/pull/1506
  
@clebertsuconic hi Clebert, perhaps I am missing something;  I am already 
extending from AbstractAction.  AbstractAction extends from ConnectionAbstract. 
 So I seem to be getting all the connectionAbstract goodness and staying with 
established pattern. It does ask for the user/password if not supplied as you 
mentions. 

thanks
Pat
 


---

[GitHub] activemq-artemis issue #1506: ARTEMIS-1384 adding CLI command (qstat) to dis...

2017-09-05 Thread clebertsuconic 
Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1506
  
Can you extend ConnectionAbstract ?

look what I do with Consumer...


if you can't connect, it will ask you for user and password through input.


I find it quite useful but it should keep the standard at least?


---

[GitHub] activemq-artemis issue #1506: ARTEMIS-1384 adding CLI command (qstat) to dis...

2017-09-05 Thread pgfox 
Github user pgfox commented on the issue:

https://github.com/apache/activemq-artemis/pull/1506
  
@jbertram Thanks Justin. I will move it under the queue group as you 
suggested. 




---

[GitHub] activemq-artemis issue #1506: ARTEMIS-1384 adding CLI command (qstat) to dis...

2017-09-05 Thread jbertram 
Github user jbertram commented on the issue:

https://github.com/apache/activemq-artemis/pull/1506
  
I think rather than having this as a "top level" command it should be 
nested under the resource type, in this case "queue" so that the command would 
be:

`./artemis queue stat ...`

I can imagine in the future we'll want to add a CLI 'stat' command for 
other resource types like address and maybe consumer.

This is a great addition, BTW.  Kudos, @pgfox. 


---

[GitHub] activemq-artemis issue #1506: ARTEMIS-1384 adding CLI command (qstat) to dis...

2017-09-05 Thread pgfox 
Github user pgfox commented on the issue:

https://github.com/apache/activemq-artemis/pull/1506
  
Updated to filter on any of the columns returned 

```
$ ./artemis qstat --user admin --password admin --field ADDRESS --operation 
EQUALS --value test500
|NAME |ADDRESS  |CONSUMER_COUNT 
|MESSAGE_COUNT |MESSAGES_ADDED |DELIVERING_COUNT |MESSAGES_ACKED |
|test500  |test500  |0  |1000   
   |1000   |0|0  |
```

--queueName=X can still be used as a shortcut to filter by "NAME that 
contains String X"

```
$ ./artemis qstat --user admin --password admin --queueName test
|NAME |ADDRESS  |CONSUMER_COUNT 
|MESSAGE_COUNT |MESSAGES_ADDED |DELIVERING_COUNT |MESSAGES_ACKED |
|test500  |test500  |0  |1000   
   |1000   |0|0  |
|test501  |test501  |0  |50 
   |50 |0|0  |
|test502  |test502  |0  |75 
   |75 |0|0  |
|test503  |test503  |0  |90 
   |90 |0|0  |
|test504  |test504  |0  |200
   |200|0|0  |

```



---

[GitHub] activemq-artemis issue #1506: ARTEMIS-1384 adding CLI command (qstat) to dis...

2017-09-04 Thread michaelandrepearce 
Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1506
  
Should the filtering (currently just queue name) be more generic, so that 
you can filter on any field (as like in web console)?


---