lowleveldesign / diagnostics-kit Goto Github PK

Hi, first thanks for sharing some great work!

Have you already implemented an sql server log store or whats the case there ?
The documentation talks about this briefly in section 3.1 "Log stores using ElasticSearch, MySql or SQL Server support " But in the repository i cant find anything beside mysql.

Many thanks //Anders

It looks like only Elasticsearch 2.x is supported. I've got this error with Elasticsearch 5.x:

[PipelineException: Failed sniffing cluster state.]
   Elasticsearch.Net.RequestPipeline.Sniff() in C:\code\elasticsearch-net\src\Elasticsearch.Net\Transport\Pipeline\RequestPipeline.cs:340
   Elasticsearch.Net.RequestPipeline.FirstPoolUsage(SemaphoreSlim semaphore) in C:\code\elasticsearch-net\src\Elasticsearch.Net\Transport\Pipeline\RequestPipeline.cs:134
   Elasticsearch.Net.Transport`1.Request(HttpMethod method, String path, PostData`1 data, IRequestParameters requestParameters) in C:\code\elasticsearch-net\src\Elasticsearch.Net\Transport\Transport.cs:53
   Elasticsearch.Net.ElasticLowLevelClient.IndicesExists(String index, Func`2 requestParameters) in C:\code\elasticsearch-net\src\Elasticsearch.Net\ElasticLowLevelClient.Generated.cs:2514
   Nest.LowLevelDispatch.IndicesExistsDispatch(IRequest`1 p) in C:\code\elasticsearch-net\src\Nest\_Generated\_LowLevelDispatch.generated.cs:1242
   Nest.ElasticClient.Nest.IHighLevelToLowLevelDispatcher.Dispatch(TRequest request, Func`3 responseGenerator, Func`3 dispatch) in C:\code\elasticsearch-net\src\Nest\ElasticClient.cs:56
   LowLevelDesign.Diagnostics.LogStore.ElasticSearch.ElasticSearchClientConfiguration..cctor() in C:\a\1\s\LogStores\LowLevelDesign.Diagnostics.LogStore.ElasticSearch\ElasticSearchClientConfiguration.cs:77

It's probably related to this issue (using NEST 2.x): elastic/elasticsearch-net#2339

I think that wiki should be updated to reflect this, because currently it states

, which is confusing, since given ElasticSearch versioning scheme it's easy to assume that 5.x is OK.

Hello, I want to test Your solusion I download diagcastle-elasticsearch_1.0.0.0.zip from github realese. and I install on IIS 8.5.

I have following error.

I don't change web.config.

Do You have some idea what to do?

I've trying to use Diagnostics Castle with ElasticSearch 2.x and having strange issues. Every HTTP request, that goes through ASP.NET takes 2-3 minutes to complete.

I've been able to narrow it using IIS failed Request Tracing to this:

As you can see, it's stuck for a minute and half in the Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContextStage.

Do you have any idea why this happens and what I can do to fix this?

Hi Sebastian

First of all many thanks for the SQL server update it works like a charm 8-)

I have an additional question related to musketeer and logging of services.

In the wiki there is a config option include-services and I have tried to configure that to monitor all services that contains "Time" this is my config

<add key="lowleveldesign.diagnostics.url" value="http://localhost:82/" />
    <add key="job:iis-config-refresh-cron" value="0 0/10 * * * ?" />
    <add key="job:perf-monitor-cron" value="0 * * * * ?" />
    <add key="job:iis-logs-read-cron" value="0/30 * * * * ?" />
    <add key="job:check-updates" value="0 /6 * * * ?" />
    <add key="include-http-success-logs" value="false" />
    <add key="include-services" value="\bTime\b;"/>

but no traces of any services can be found in the castle site. Logs from IIS and so on are being picked up but performance data (status such as sopped / running and so on) is not picked up.

It could be that i have missed something here (most likely) or can this type of monitoring not be applied?

The intended use case is to be able to collect some general status about some critical third-party services, hence its not possible to add a harvester like I can for services where i can control the code.

Many thanks //Anders