-
I think our current approach to logstash filter configuration is too fragile. I think `logsearch-boshrelease` should manage the architecture and define the conventions, but have minimal impact on its …
-
This has been triggered by #90 and relates to #88 - the [Redis FAQ](http://redis.io/topics/faq) _What happens if Redis runs out of memory?_ seems to suggest that the virtual memory based solution ment…
sopel updated
9 years ago
-
Since logstash 1.4, stdout no longer support the `debug` field.
(jobs/ingestor_syslog/templates/config/syslog_to_redis.conf.erb)[https://github.com/logsearch/logsearch-boshrelease/blob/master/jobs/in…
-
Michael Tekel says,
> Blobstore error: Failed to find object
> 'b9e969e6-3ad5-4c6b-b39e-a03b471f4ea0', S3 response error: The AWS
> Access Key Id you provided does not exist in our records.
> Could y…
-
Trying to use the new Table / Stats button in Kibana v3.1.0 (eg, [on this dashboard](http://kibana-pr10.apps.cityindex.logsearch.io/#/dashboard/elasticsearch/IP%20Diagnostics%20-%20LIVE) ) fails with:…
-
I think we design the config as if this is a core BOSH feature (in the hope that we can make that happen)
Thus, rather than prefixing all properties with `plugin.log.`, I think they should just be `l…
-
@mrdavidlaing, we should discuss putting kibana's assets in a versioned directory or using a cache-busting query param to avoid https://www.flowdock.com/app/cityindexlabs/cityindex-logsearch-io-suppor…
-
As per discussion on https://github.com/logsearch/logsearch-boshrelease/issues/10, extra filter repos should be named _logsearch_-filters-{name}
-
This has been extracted from #149: We currently facilitate Redis for the inbound log queue, however, it is not designed for clustering at all:
> With Redis, a dataset cannot grow beyond a single mast…
sopel updated
10 years ago
-
Primarily for debugging, but it'd be convenient to allow direct access to documents by ID. The regex should probably just allow all `GET`s to `/{index}/{type}/[^_].+`.
For example... this document is…