looks nice, I'll test it. Nevertheless, you have a little typo in your
installation docu: the right url is /domain:port/_plugin/HQ/ (capitol
letters at the end).
Cheers,
Andrej
Am Donnerstag, 11. Juli 2013 16:16:55 UTC+2 schrieb Roy Russo:
Hello fellow Elastickers,
A short post on the new features found in 0.95 of Elastic HQ Monitoring
and Management for ES.
New Features:
Manage Aliases: Create, Delete Index Aliases
Live Polling: All screens now have active polling, as a true
dashboard app would.
Index Health: Index Health information added to Index view screen
On Thursday, July 11, 2013 10:46:29 AM UTC-4, Andrej Rosenheinrich wrote:
Hi Roy,
looks nice, I'll test it. Nevertheless, you have a little typo in your
installation docu: the right url is /domain:port/_plugin/HQ/ (capitol
letters at the end).
Cheers,
Andrej
Am Donnerstag, 11. Juli 2013 16:16:55 UTC+2 schrieb Roy Russo:so
nice tool! One thing I noticed: my indices are all lower case named. But
the table of indices lists all indices with a capitol letter at the
beginning. That is a bit confusing.
I capped the index names, to make things pretty for aesthetic reasons, but
I can see why that would be confusing. I'll make an issue. Thanks!
On Monday, July 15, 2013 8:43:01 AM UTC-4, Andrej Rosenheinrich wrote:
Hi Roy,
nice tool! One thing I noticed: my indices are all lower case named. But
the table of indices lists all indices with a capitol letter at the
beginning. That is a bit confusing.
Hey Roy, this looks pretty cool. Have you put any thought on creating ACLs
, so that destructive actions are available only for a given list of users
/ group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the interface?
Any insights on this, if you have any, or suggestions on the best way to
add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
btw, i realise if you run this fully on your browser, the control would
have to reside elsewhere (nginx in front of ES, for example). that's fine.
I'm just not sure how things would change if installed as a "ES plugin" ..
On Tue, Jul 16, 2013 at 12:42 AM, Norberto Meijome numard@gmail.com wrote:
Hey Roy, this looks pretty cool. Have you put any thought on creating ACLs
, so that destructive actions are available only for a given list of users
/ group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the
interface?
Any insights on this, if you have any, or suggestions on the best way to
add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
I originally considered it, when I started the project but decided against
going down that road. Regardless of how this is deployed, it is still
browser-based and to my knowledge, ES doesn't have any built-in ACL, so
unfortunately it stays open for now. The best I've done is to add
confirmation/warnings before someone performs a delete action or any
unreversible action.
Regards,
Roy
On Monday, July 15, 2013 10:44:10 AM UTC-4, Norberto Meijome wrote:
btw, i realise if you run this fully on your browser, the control would
have to reside elsewhere (nginx in front of ES, for example). that's fine.
I'm just not sure how things would change if installed as a "ES plugin" ..
On Tue, Jul 16, 2013 at 12:42 AM, Norberto Meijome <num...@gmail.com<javascript:>
wrote:
Hey Roy, this looks pretty cool. Have you put any thought on creating
ACLs , so that destructive actions are available only for a given list of
users / group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the
interface?
Any insights on this, if you have any, or suggestions on the best way to
add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
cheers,
Beto
On Fri, Jul 12, 2013 at 12:16 AM, Roy Russo <royr...@gmail.com<javascript:>
wrote:
Hello fellow Elastickers,
A short post on the new features found in 0.95 of Elastic HQ Monitoring
and Management for ES.
New Features:
Manage Aliases: Create, Delete Index Aliases
Live Polling: All screens now have active polling, as a true
dashboard app would.
Index Health: Index Health information added to Index view screen
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Tried to install on a 24-node ES 0.90.2 system. It just hangs. I
installed via plugin:
$ bin/plugin -i royrusso/elasticsearch-HQ
-> Installing royrusso/elasticsearch-HQ...
Trying https://github.com/royrusso/elasticsearch-HQ/zipball/master...
(assuming site plugin)
Downloading ...........................................DONE
Identified as a _site plugin, moving to _site structure ...
Installed HQ
Does the plugin require a cluster restart before becoming active?
On Mon, Jul 15, 2013 at 9:44 AM, Norberto Meijome numard@gmail.com wrote:
btw, i realise if you run this fully on your browser, the control would
have to reside elsewhere (nginx in front of ES, for example). that's fine.
I'm just not sure how things would change if installed as a "ES plugin" ..
On Tue, Jul 16, 2013 at 12:42 AM, Norberto Meijome numard@gmail.comwrote:
Hey Roy, this looks pretty cool. Have you put any thought on creating
ACLs , so that destructive actions are available only for a given list of
users / group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the
interface?
Any insights on this, if you have any, or suggestions on the best way to
add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
Where does it hang? Are you able to reach /domain:port/_plugin/HQ/ ?
No need to restart before running. ES simply serves up the JS/HTML on its
own.
On Tuesday, July 16, 2013 10:51:46 AM UTC-4, Kenneth Loafman wrote:
Tried to install on a 24-node ES 0.90.2 system. It just hangs. I
installed via plugin:
$ bin/plugin -i royrusso/elasticsearch-HQ
-> Installing royrusso/elasticsearch-HQ...
Trying https://github.com/royrusso/elasticsearch-HQ/zipball/master...
(assuming site plugin)
Downloading ...........................................DONE
Identified as a _site plugin, moving to _site structure ...
Installed HQ
Does the plugin require a cluster restart before becoming active?
On Mon, Jul 15, 2013 at 9:44 AM, Norberto Meijome <num...@gmail.com<javascript:>
wrote:
btw, i realise if you run this fully on your browser, the control would
have to reside elsewhere (nginx in front of ES, for example). that's fine.
I'm just not sure how things would change if installed as a "ES plugin" ..
On Tue, Jul 16, 2013 at 12:42 AM, Norberto Meijome <num...@gmail.com<javascript:>
wrote:
Hey Roy, this looks pretty cool. Have you put any thought on creating
ACLs , so that destructive actions are available only for a given list of
users / group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the
interface?
Any insights on this, if you have any, or suggestions on the best way to
add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
cheers,
Beto
On Fri, Jul 12, 2013 at 12:16 AM, Roy Russo <royr...@gmail.com<javascript:>
wrote:
Hello fellow Elastickers,
A short post on the new features found in 0.95 of Elastic HQ Monitoring
and Management for ES.
New Features:
Manage Aliases: Create, Delete Index Aliases
Live Polling: All screens now have active polling, as a true
dashboard app would.
Index Health: Index Health information added to Index view
screen
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
Norberto 'Beto' Meijome
--
Norberto 'Beto' Meijome
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
Does the plugin require a cluster restart before becoming active?
On Mon, Jul 15, 2013 at 9:44 AM, Norberto Meijome num...@gmail.comwrote:
btw, i realise if you run this fully on your browser, the control would
have to reside elsewhere (nginx in front of ES, for example). that's fine.
I'm just not sure how things would change if installed as a "ES plugin" ..
On Tue, Jul 16, 2013 at 12:42 AM, Norberto Meijome num...@gmail.comwrote:
Hey Roy, this looks pretty cool. Have you put any thought on creating
ACLs , so that destructive actions are available only for a given list of
users / group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the
interface?
Any insights on this, if you have any, or suggestions on the best way
to add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
cheers,
Beto
On Fri, Jul 12, 2013 at 12:16 AM, Roy Russo royr...@gmail.com wrote:
Hello fellow Elastickers,
A short post on the new features found in 0.95 of Elastic HQ
Monitoring and Management for ES.
New Features:
Manage Aliases: Create, Delete Index Aliases
Live Polling: All screens now have active polling, as a true
dashboard app would.
Index Health: Index Health information added to Index view
screen
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
No problem.. I guess more of a reason to use the ES thrift interface for
apps, leave http for management and impose restrictions via nginx in front
of ES.
Cheers,
On 19/07/2013 7:31 AM, "Roy Russo" royrusso@gmail.com wrote:
I originally considered it, when I started the project but decided against
going down that road. Regardless of how this is deployed, it is still
browser-based and to my knowledge, ES doesn't have any built-in ACL, so
unfortunately it stays open for now. The best I've done is to add
confirmation/warnings before someone performs a delete action or any
unreversible action.
Regards,
Roy
On Monday, July 15, 2013 10:44:10 AM UTC-4, Norberto Meijome wrote:
btw, i realise if you run this fully on your browser, the control would
have to reside elsewhere (nginx in front of ES, for example). that's fine.
I'm just not sure how things would change if installed as a "ES plugin" ..
On Tue, Jul 16, 2013 at 12:42 AM, Norberto Meijome num...@gmail.comwrote:
Hey Roy, this looks pretty cool. Have you put any thought on creating
ACLs , so that destructive actions are available only for a given list of
users / group ( could be htauth based, for all I really care)?
or maybe a simple way to remove all destructive commands from the
interface?
Any insights on this, if you have any, or suggestions on the best way to
add this functionality would be great ( caveat, i havent checked out the
code just yet, so maybe just tell me to rtfm )
cheers,
Beto
On Fri, Jul 12, 2013 at 12:16 AM, Roy Russo royr...@gmail.com wrote:
Hello fellow Elastickers,
A short post on the new features found in 0.95 of Elastic HQ Monitoring
and Management for ES.
New Features:
Manage Aliases: Create, Delete Index Aliases
Live Polling: All screens now have active polling, as a true
dashboard app would.
Index Health: Index Health information added to Index view
screen
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
