You may want to give this a try:
https://github.com/synhershko/KibanaDotNet/tree/owin
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Lucene.NET committer and PMC member
On Mon, Jan 26, 2015 at 3:58 PM, GWired
https://lh4.googleusercontent.com/-wPfu7feblyk/VMY6yMO1mzI/AI4/OE29HIVU2Lw/s1600/output-optimised.gif
Hi,
We tried to create panels based on Filters Aggregation on the latest Kibana
source, and we encountered the following problems:
1) Buckets from Filters aggregation are not
AFAIK, Kibana by default saves it's dashboards in an ES index called
kibana-int, as referenced in your httpd.conf file here: LocationMatch
^/(kibana-int/dashboard/|kibana-int/temp)(.*)$
You could restrict commands on that index based on authentication, like x
user can do GET POST, whereas y
document: {
properties: {
text: {
type: string,
store: true,
index: analyzed,
term_vector: with_positions_offsets_payloads,
filter: stopper,
analyzer:
Hi,
Has anyone encountered a problem with logstash where there are several
filters (~8 grok filters, multiline and json) that causes logstash to get
stuck when sending bulk of actions to elasticsearch ?
I tried playing with the amount of filters to see if that what causes the
issue.
- Only
Yes, there is a version for ES 1.3.4
Jörg
On Fri, Jan 23, 2015 at 7:13 PM, bbehling brian.behl...@gmail.com wrote:
Jörg,
Will your plugin work with ES version 1.3.4?
--
View this message in context:
Thanks for you quick help!
Am Montag, 26. Januar 2015 13:15:26 UTC+1 schrieb Jörg Prante:
You should delete the river instance after usage. Otherwise, the river is
executed each time the node starts.
Jörg
On Mon, Jan 26, 2015 at 1:09 PM, Abid Hussain hus...@novacom.mygbiz.com
Sure it's:
elasticsearch: /elasticsearch/,
On Friday, January 23, 2015 at 5:08:59 PM UTC-5, Mark Walkom wrote:
Can you post the applicable line from your kibana config that points to ES?
On 24 January 2015 at 07:50, Scott Lee sl...@navteca.com javascript:
wrote:
Hello, I am new to the
On Monday, January 26, 2015 at 14:58 CET,
GWired garrettcjohn...@gmail.com wrote:
I was able to get Kibana setup on my localhost and did a generic entry
to allow everything into the elasticsearch.yml
http.cors.allow-origin: /.*/
Now I'm trying to getting it to run on my remote server
Hi,
I am using version 1.3.7 and have problems with dynamic mappings of
complex fields and filters. It seems this is not supported as I cannot
obtain the results, but get an empty set response each time.
I have found this link suggesting the
same
Yes,
It works when I'm on my localhost serving it to me connected to a remote
elasticsearch. It just isn't working when I'm serving it from a dedicated
Windows 2008 web server connected to the same remote elasticsearch.
Config Working:
Desktop: IIS 8 installed on Windows 8.1 - Kibana
I have done test and found out following:
{
query: {
filtered: {
query: {
query_string: {
query: uri:video\\-ondemand\/video\/flv\/test\/
}
},
filter: {
bool: {
must: [
{
range: {
@timestamp: {
from: 2014-12-01T00:00:00.001,
to: 2014-12-01T23:59:59.999
}
}
}
]
}
}
}
},
size: 100
}
Il 21/01/2015 11:43, Alessandro
Bonfanti ha scritto:
Il 02/12/2014 09:21, Alessandro
Bonfanti ha scritto:
Il 12/11/2014 17:43, Alessandro
Bonfanti ha scritto:
Il
I was able to get Kibana setup on my localhost and did a generic entry to
allow everything into the elasticsearch.yml
http.cors.allow-origin: /.*/
Now I'm trying to getting it to run on my remote server running IIS 7.5 on
port 8080.
The page loads but only the top bar loads and nothing else
Is there a place where someone can point me to a simple set of instructions
for adding a node to an Elastic Search cluster?
I think I understand Sharding and Nodes and that's what the documents do is
talk about them.
But what I don't understand is...
How do install ElasticSearch on the
Hey, it is as simple as running the first node. Just install ES, select a
cluster name for the nodes, start it on the nodes, and let the node
discovery join the nodes. I recommend odd numbers and at least 3 nodes to
avoid a split brain.
Or did I miss something?
Jörg
On Mon, Jan 26, 2015 at
Thanks David... I got the idea.
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web
I could do that - I'll have to see if I can trim it down to a reasonable
size without all the unrelated code in it.
Is it obvious on GitHub where people can submit error samples? I haven't
done that before.
- Tim
On Friday, January 23, 2015 at 1:27:05 AM UTC-8, David Pilato wrote:
Yes I am.
It always easier to share a project for which we only have to do:
git clone
mvn install
But, you could also share on gist.github.com a pom.xml and a test class.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 26 janv. 2015 à 19:27, TimOnGmail timbes...@gmail.com a écrit
Hi all,
So I have an ES cluster that is currently exhibiting the following
properties:
If I do:
curl -k -vv http://elasticsearch.example.com:9200/logstash*/_search
The request returns properly with the expected results (I get a 200 OK
with the search results).
If I do:
curl -k -vv
Opening an index is a costly operation.
Creating a new index is not.
My 2 cents
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs
Le 26 janv.
I'm doing this in windows.
I'm crossing internal domains for each node so I thought I'd have to tell
something somewhere that there is another node.
Also I probably want it configured the same way.
Also I don't see where I select a cluster name for the nodes.
With the single node install
I agree. But they both go thru shard allocation, no? I’m assuming
opening/closing small 1 shard indexes (max 100MB total size) shouldn’t be that
bad.
On Jan 26, 2015, at 12:42 PM, David Pilato da...@pilato.fr wrote:
Opening an index is a costly operation.
Creating a new index is not.
Could you try replacing True by true?
David
Le 26 janv. 2015 à 22:49, Xavier Garcia x...@vier.im a écrit :
Hello guy,
I'm configuring a ES cluster and i got this issue -
ElasticsearchIllegalArgumentException[value cannot be parsed to boolean [
true/1/on/yes OR false/0/off/no ] ]
I
Already try but doesn't work.
Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
Could you try replacing True by true?
David
Le 26 janv. 2015 à 22:49, Xavier Garcia x...@vier.im javascript: a
écrit :
Hello guy,
I'm configuring a ES cluster and i got this issue -
Hello guy,
I'm configuring a ES cluster and i got this issue -
*ElasticsearchIllegalArgumentException[value
cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ] ]*
I try to increase the level of logging but nothing work i can't find the
right line, do you have any idea where is
Hi,
Is there a way to tell ES to open closed indices automatically on first access
(search or indexing)? I can do it on the application side by looking for
IndexClosedException, but this seems like a natural thing that ES should be
able to do, after all ES creates new indices automatically.
-
Correction - the body of the request was messed up because I was trying to
reorder its content. The correct PUT body is and error are:
$ curl -XPUT 'http://localhost:9200/_snapshot/amos0' -d '{
s3dev0: {
settings: {
base_path: elasticsearch/prod/snapshots0,
Correction - the body of the request was messed up because I was trying to
reorder its content. The correct PUT body is and error are:
$ curl -XPUT 'http://localhost:9200/_snapshot/amos0' -d '{
s3dev0: {
settings: {
base_path: elasticsearch/dev/snapshots0,
Did you that while elasticsearch was running?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 07:46, phani.nadimi...@goktree.com a écrit :
yes David i changed permissions recursively.
On Tuesday, January 27, 2015 at 12:03:14 PM UTC+5:30, David Pilato
Thanks David,
That would explain it.
Is there a way to skip the validation?
On Tuesday, 27 January 2015 16:52:11 UTC+11, David Pilato wrote:
IIRC when you create a repository we first try to validate it by writing a
sample file in it.
As you set it to read only, I guess it could be the
Any idea ? Someone know if a configuration validator exist for
ElasticSearch? Or how i can improve the loggin to find which line it's
Thank you,
Le lundi 26 janvier 2015 15:13:09 UTC-8, Xavier Garcia a écrit :
Yep False so and rewrite all number i can, change the charset of file.
It's crasy
No David , First i copied indices folder under nodes/0 (old cluster
data dir) and copied to new cluster and changed permission to elastic
search but when i tried to access the index it is showing index missing
exception even though index resides in data folder.
Next i deleted the indices
IIRC when you create a repository we first try to validate it by writing a
sample file in it.
As you set it to read only, I guess it could be the cause.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 06:20, Amos S amos.shap...@gmail.com a écrit :
No David Mycluster name on the new server was changed.is this be a problem?
On Tuesday, January 27, 2015 at 12:19:58 PM UTC+5:30, David Pilato wrote:
Are you sure you have same config file on new server?
I mean cluster name?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr /
Could you test this config locally and add one setting at a time and check
which one is incorrect?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 06:39, Xavier Garcia x...@vier.im a écrit :
Any idea ? Someone know if a configuration validator exist for
Could you try to set verify to false?
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html#_repositories
Not sure if it works but would love to know.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 07:09, Amos S
Are you sure you have same config file on new server?
I mean cluster name?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 07:46, phani.nadimi...@goktree.com a écrit :
yes David i changed permissions recursively.
On Tuesday, January 27, 2015 at
Hi David,
We need to copy Entire data folder or indices folder from existing
cluster to other cluster when i did this the elastic search server not
detecting the indices we copied , and it is showing indices are not
recovered in to cluster state and when i access the index it is not showing
Hi David,
We need to copy Entire data folder or indices folder from existing
cluster to other cluster when i did this the elastic search server not
detecting the indices we copied , and it is showing indices are not
recovered in to cluster state and when i access the index it is not showing
Yes. Data dir naming is:
/data/clustername/nodes/…
So if you change the cluster name…
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs
Le
Did you copy the full data dir?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 06:13, phani.nadimi...@goktree.com a écrit :
Hi David,
We need to copy Entire data folder or indices folder from existing cluster
to other cluster when i did this
Hello,
For some investigation work, I'm trying to restore specific indices from
our production ES cluster to a single one-off node.
We run a cluster of ES 1.4.2 on EC2, the data is stored locally on each EC2
instance with snapshots stored on an S3 bucket.
I've setup a one-off EC2 instance and
yes David i changed permissions recursively.
On Tuesday, January 27, 2015 at 12:03:14 PM UTC+5:30, David Pilato wrote:
Did you change permission recursively ?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 06:39, phani.n...@goktree.com javascript: a
You don't need the plugin, it can make discovery easier though.
You haven't bound ES to localhost only have you?
On 27 January 2015 at 09:42, Dave Mittner dave.mitt...@gmail.com wrote:
I'm at a bit of a loss here...
I have a pretty standard setup of elasticsearch and I'm able to
curl/telnet
I'm binding to localhost; nothing else seems to work. I get Failed to
bind errors in the log if I try using the actual hostname.
On Monday, January 26, 2015 at 5:04:34 PM UTC-7, James Carr wrote:
* make sure you haven't bound to 127.0.0.1
* make sure relevant security groups have been opened.
You should bind to 0.0.0.0 not localhost. Then you can hit it remotely.
You can also use a reverse-proxy. It is what we do :-)
On Mon, Jan 26, 2015 at 6:16 PM, Dave Mittner dave.mitt...@gmail.com
wrote:
I'm binding to localhost; nothing else seems to work. I get Failed to
bind errors in the
Did you change permission recursively ?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 27 janv. 2015 à 06:39, phani.nadimi...@goktree.com a écrit :
No David , First i copied indices folder under nodes/0 (old cluster data
dir) and copied to new cluster and
So here more details:
{
query: {
filtered: {
query: {
query_string: {
query: uri:video\\-ondemand\/video\/flv\/test\/ # one thing with
video\-ondemand I get an Error ( nested: JsonParseException[Unrecognized
character escape '-' (code 45))
}
},
filter: {
bool: {
must: [
{
range: {
Can you use a filter agg?
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-filter-aggregation.html
David
Le 26 janv. 2015 à 09:46, Radim Novotny novotny.ra...@gmail.com a écrit :
Hi,
I'm using ES 1.4.2 to search across 4 slightly different
I have no idea but for sure, I'd prefer using a term filter on uri field and I
would not set _cache.
But may be you could GIST a full example we can reproduce?
David
Le 26 janv. 2015 à 08:47, Messias torsten.schub...@gl-systemhaus.de a écrit
:
Hi,
I have some issue with a filtered
Hi,
A common approach for replicating changes across multiple geographically
distributed clusters if to put a message queue in front of Elasticsearch
and feed all data modifications through this so that they can be applied to
the clusters independently. This allows issues with unreliable
Jörg,
Will your plugin work with ES version 1.3.4?
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Sorting-strings-that-contain-numbers-tp4024553p4069501.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
You received this message
So I also looked at logstash, but you have to define the field names for each
file. Same as the others.
Logstash is almost worse because you need a restart of the service when you
update the config file.
--
You received this message because you are subscribed to the Google Groups
Hi,
I'm using ES 1.4.2 to search across 4 slightly different types in a single
index. The following example is simplified version with only two types
profile and publication. Profiles can have related publications,
publications can have related profiles.
I want to do a full text search
Range and sort are two different challenges.
There is one solution for sort using a custom analyzer. You can create
binary sort keys for natural sort.
Use
https://github.com/jprante/elasticsearch-analysis-naturalsort
and try this example
PUT /test/
{
index: {
analysis: {
I'm having this problem as well. I opened a bug for it
here: https://github.com/elasticsearch/elasticsearch/issues/9410
On Friday, January 16, 2015 at 4:29:06 AM UTC-8, Ipatios Asmanidis wrote:
Using version : 1.4.2
OS: Ubuntu Linux 14.04
JVM: 1.7
Here is how you can reproduce the issue
Hi all,
I configured a river for one-time indexing like:
PUT /_river/my_river/_meta
{
type: jdbc,
jdbc: {
driver: com.mysql.jdbc.Driver,
url: jdbc:mysql://192.168.110.180:3306/my_db,
user: user,
password: password,
index: my_idx,
Looks solid,
I'll give it a run today.
On Sunday, January 25, 2015 at 7:57:29 AM UTC-5, Jörg Prante wrote:
I finally managed to modify the CsvJdbc driver from
http://csvjdbc.sourceforge.net/ so it behaves nicely and pushed it to
https://github.com/jprante/jdbc-driver-csv
So the news
You should delete the river instance after usage. Otherwise, the river is
executed each time the node starts.
Jörg
On Mon, Jan 26, 2015 at 1:09 PM, Abid Hussain huss...@novacom.mygbiz.com
wrote:
Hi all,
I configured a river for one-time indexing like:
PUT /_river/my_river/_meta
{
I have this JSON object where I wish to change the scoring function of the
search query:
POST /index/document/_search
{
query: {
function_score: {
query: {match: {_all: fox}},
script_score: {
script: _score
}
}
}
}
I want to change the score function so
Of course, you did it for False as well?
David
Le 26 janv. 2015 à 23:14, Xavier Garcia x...@vier.im a écrit :
Already try but doesn't work.
Le lundi 26 janvier 2015 14:08:39 UTC-8, David Pilato a écrit :
Could you try replacing True by true?
David
Le 26 janv. 2015 à 22:49,
That's still massively different to creating and allocating a completely
empty index.
On 27 January 2015 at 08:23, Drew Kutcharian d...@venarc.com wrote:
I agree. But they both go thru shard allocation, no? I’m assuming
opening/closing small 1 shard indexes (max 100MB total size) shouldn’t be
I'm at a bit of a loss here...
I have a pretty standard setup of elasticsearch and I'm able to curl/telnet
to port 9200 locally, but the connection is refused if accessed from
another server. I'm likewise unable to connect to port 9300. For Kibana3
I've also added:
http.cors.allow-origin: *
If you just downloaded and started ES then your settings will be default
ones.
Change cluster.name to something that isn't elasticsearch, and make sure it
is the same on both nodes.
Just list both hosts under discovery.zen.ping.unicast.hosts. Also make sure
you disable multicast at the same time.
That doesn't look valid, it should be more like elasticsearch: http://
elasticsearch:9200,
If elasticsearch is the DNS name of your node.
On 27 January 2015 at 00:20, Scott Lee s...@navteca.com wrote:
Sure it's:
elasticsearch: /elasticsearch/,
On Friday, January 23, 2015 at 5:08:59 PM
I have a dynamic template that sets up not_analyzed raw mappings for all my
string fields.
When I perform a query search like this:
field.raw=KnownValue
it works (has hits).
When I do this:
field.raw=Known?alue
it doesn't return any data (? wildcard doesn't work).
However,
field.raw=*
does
Yep False so and rewrite all number i can, change the charset of file. It's
crasy i don't understabd what happend.
Le lundi 26 janvier 2015 14:32:40 UTC-8, David Pilato a écrit :
Of course, you did it for False as well?
David
Le 26 janv. 2015 à 23:14, Xavier Garcia x...@vier.im
* make sure you haven't bound to 127.0.0.1
* make sure relevant security groups have been opened.
On Mon, Jan 26, 2015 at 5:58 PM, Mark Walkom markwal...@gmail.com wrote:
You don't need the plugin, it can make discovery easier though.
You haven't bound ES to localhost only have you?
On 27
For a well formatted example, please
see:
http://stackoverflow.com/questions/28161480/fuzzy-not-functioning-as-expected-one-term-search-see-example
Here's my problem:
Consider the following results from:
curl -XGET 'http://localhost:9200/megacorp/employee/_search' -d
'{ query :
Without seeing the code, I guess your ES cluster is a bit slow in starting
up new shards, which is pretty normal. There is a small time span after
index creation and getting ready for accepting docs. You should wait for
the created index to get initialized. Usually this is not required, because
Ok so I looked at the config file and found this:
cluster.name - which you are saying I set it to the same on both
machines... got it.
discovery.zen.ping.unicast.hosts: [host1, host2:port]--- since I
am not on the same network in this case they are in different but
accessible domains
We're storing Kibana-style time series documents across three indexes on a
10 node cluster (i2.xlarges). These indexes have between 20M-500M docs at
peak and we use bool filters extensively while querying. Query volumes are
pretty low (maybe around 100 searches/sec at peak) versus index ops
73 matches
Mail list logo