Seq Forwarder v1.1.73 issues

astavria4 commented 5 years ago

Hello,

I recently installed Seq Forwarder v1.1.73 on my local machine to test. When I first installed, the buffer directory was not created ( I had to manually create it myself).

From reading previous posts, v1.0.69 supports API key forwarding. If I were to leave the API key section in the Seq Forwarder Configuration screen blank and instantiate the Logger as below, the error does not get to the Seq Server and I get this in the log: {"@t":"2018-12-04T15:12:16.3846093Z","@m":"The default buffer is empty and will be removed until more data is received","@i":"745bce03","SourceContext":"Seq.Forwarder.Multiplexing.ActiveLogBufferMap"}


Log.Logger = new LoggerConfiguration()
                .WriteTo.Seq("http://localhost:15341",_logLevel, apiKey: _apiKey, compact: true)
                .CreateLogger();

            Log.Error(exception,"");

            Log.CloseAndFlush();

Am I doing something wrong here?

nblumhardt commented 5 years ago

Hi, and thanks for checking this out. Your sample looks fine, although it's unusual to see a "" empty message in there.

Does the same code send events successfully if no API key is used, and it's instead set in the forwarder configuration?

Best regards, Nick

astavria4 commented 5 years ago

Hi Nick,

You are correct. The same code sends events successfully if no API key is used, and it's instead set in the forwarder configuration.

Thanks, Alex

From: Nicholas Blumhardt notifications@github.com Sent: Tuesday, December 4, 2018 7:15 PM To: datalust/seq-forwarder Cc: Stavrianidis, Alex; Author Subject: Re: [datalust/seq-forwarder] Seq Forwarder v1.1.73 issues (#41)

Hi, and thanks for checking this out. Your sample looks fine, although it's unusual to see a"" empty message in there.

Does the same code send events successfully if no API key is used, and it's instead set in the forwarder configuration?

Best regards, Nick

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_datalust_seq-2Dforwarder_issues_41-23issuecomment-2D444309102&d=DwMFaQ&c=ezHeX61fxv1UK0GsNdSebQ&r=VccsJVkOmpufD4SOuI375viQoPmRABym-9Vl7De-Spk&m=cle9syKZkG_YR1EV5y_gJfN2kupjTM1VWcC3gk3NsO4&s=EjCsZYtg85ihKqntig9yBBQRvdhgYrg-5Wuor9Xf0BY&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AUWiofKEamTkffRxRWXWrClLBXScKz9-5Fks5u1xAhgaJpZM4ZA4EV&d=DwMFaQ&c=ezHeX61fxv1UK0GsNdSebQ&r=VccsJVkOmpufD4SOuI375viQoPmRABym-9Vl7De-Spk&m=cle9syKZkG_YR1EV5y_gJfN2kupjTM1VWcC3gk3NsO4&s=3j_XoLXtTr9_yTHGywaV3rx_OeTY6aqvuxp9Xc6ApIs&e=.

nblumhardt commented 5 years ago

Thanks for the follow-up. We'll take a closer look and see what other failure paths are possible, here.

astavria4 commented 5 years ago

Thanks. We would like to use Seq Forwarder for all of our applications but we need to have unique api keys per app.

Thanks, Alex

From: Nicholas Blumhardt notifications@github.com Sent: Wednesday, December 5, 2018 3:40 PM To: datalust/seq-forwarder Cc: Stavrianidis, Alex; Author Subject: Re: [datalust/seq-forwarder] Seq Forwarder v1.1.73 issues (#41)

Thanks for the follow-up. We'll take a closer look and see what other failure paths are possible, here.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_datalust_seq-2Dforwarder_issues_41-23issuecomment-2D444638637&d=DwMCaQ&c=ezHeX61fxv1UK0GsNdSebQ&r=VccsJVkOmpufD4SOuI375viQoPmRABym-9Vl7De-Spk&m=PZdP4ibI7dkiVUF-odnw8RHIpl05BdnrfDh2psUFKAA&s=UyshZdJgGZO7ispp6z4Kxpg1_anDOKjGuOpinR846T4&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AUWioUNaM4QXslhNLLudcYEUvf9ki1ICks5u2C8mgaJpZM4ZA4EV&d=DwMCaQ&c=ezHeX61fxv1UK0GsNdSebQ&r=VccsJVkOmpufD4SOuI375viQoPmRABym-9Vl7De-Spk&m=PZdP4ibI7dkiVUF-odnw8RHIpl05BdnrfDh2psUFKAA&s=qOoBH_T6CELHS6QyULFXh3S1WbCTNk51-BfMEYz12WU&e=.

astavria commented 5 years ago

per your suggestion, removing compact: true

from Log.Logger = new LoggerConfiguration() .WriteTo.Seq("http://localhost:15341",_logLevel, apiKey: _apiKey, compact: true) .CreateLogger();

fixed this issue.

Thanks for working with me!

nblumhardt commented 5 years ago

:tada:

datalust / seq-forwarder

Seq Forwarder v1.1.73 issues #41