0.85.0 version not shipping logs

[vberegov]

Using simple configuration to deliver logs :

receivers:
filelog:
start_at: beginning
include:
- /home/ubuntu/1
multiline:
line_start_pattern: "^{"
operators:
- type: json_parser
parse_to: body
exporters:
logdelivery:
domain: "domain.com"
private_key: "xxxx-xxxxx-xxxx-xxxx-xxxx"
application_name: "open-test-app"
subsystem_name: "test-app"
timeout: 30s
service:
pipelines:
logs:
receivers: [ filelog ]
exporters: [ logdelivery ]

With version 85 files are not being shipped over to logdelivery endpoint, even after triggering the file with additional data. Version 83 works absolute fine with the same config

[crobert-1]

Hello @vberegov, pardon my ignorance, but I'm not familiar with any exporter named logdelivery. Can you direct me to it?

[vberegov]

Hi @crobert-1 thanks a lot for your response. logdelivery is the name of the defined exporter above :

logdelivery:
domain: "domain.com"
private_key: "xxxx-xxxxx-xxxx-xxxx-xxxx"

[crobert-1]

Can you share the errors you're seeing from the collector so we can help debug the issue?

[vberegov]

there are no errors ... it just no shipping the log file. 0.83 same config works fine Regards , Beregovsky Vadim

[crobert-1]

Hi @crobert-1 thanks a lot for your response. logdelivery is the name of the defined exporter above :

logdelivery: domain: "domain.com" private_key: "xxxx-xxxxx-xxxx-xxxx-xxxx"

My apologies for the confusion here, but when I attempt to run a demo similar to what you have in your configuration file, I get an error because there is no exporter named logdelivery when I declare it in the config.

Here's my output:

* error decoding 'exporters': unknown type: "logdelivery" for id: "logdelivery" (valid values: [alibabacloud_logservice awskinesis datadog googlecloudpubsub prometheus awsxray clickhouse googlecloud opencensus signalfx zipkin azuredataexplorer dataset pulsar sumologic cassandra parquet splunk_hec tencentcloud_logservice awsemf carbon elasticsearch influxdb kafka logzio otlphttp awscloudwatchlogs file loadbalancing sapm tanzuobservability skywalking otlp coralogix f5cloud googlemanagedprometheus logicmonitor prometheusremotewrite sentry logging awss3 azuremonitor dynatrace instana loki mezmo])

This means that the collector is going through the config file trying to setup all of the components required, but when it sees the logdelivery exporter it fails because there aren't any components of that name within the collector itself.

Is there any link to the logdelivery exporter you're attempting to use? Like a README or documentation on how to use it?

[vberegov]

Curtis, it's just a naming - there is no specific identification of the exporter here. The definition of this exporter is within the body of config file. Let me know if it makes sense Thanks

…

On Fri, Oct 6, 2023 at 1:06 PM Curtis Robert ***@***.***> wrote: Hi @crobert-1 <https://github.com/crobert-1> thanks a lot for your response. logdelivery is the name of the defined exporter above : logdelivery: domain: "domain.com" private_key: "xxxx-xxxxx-xxxx-xxxx-xxxx" My apologies for the confusion here, but when I attempt to run a demo similar to what you have in your configuration file, I get an error because there is no exporter named logdelivery. Here's my output: * error decoding 'exporters': unknown type: "logdelivery" for id: "logdelivery" (valid values: [alibabacloud_logservice awskinesis datadog googlecloudpubsub prometheus awsxray clickhouse googlecloud opencensus signalfx zipkin azuredataexplorer dataset pulsar sumologic cassandra parquet splunk_hec tencentcloud_logservice awsemf carbon elasticsearch influxdb kafka logzio otlphttp awscloudwatchlogs file loadbalancing sapm tanzuobservability skywalking otlp coralogix f5cloud googlemanagedprometheus logicmonitor prometheusremotewrite sentry logging awss3 azuremonitor dynatrace instana loki mezmo]) Is there any link to the logdelivery exporter you're attempting to use? Like a README or documentation on how to use it? — Reply to this email directly, view it on GitHub <#27202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS24LQUSIFPH6C672HTMRJ3X6A27VAVCNFSM6AAAAAA5HQJRIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGEYTSOBQGA> . You are receiving this because you were mentioned.Message ID: <open-telemetry/opentelemetry-collector-contrib/issues/27202/1751119800@ github.com>

-- Regards , Beregovsky Vadim

[crobert-1]

Sorry for the confusion here. When an exporter is defined in the config file (logdelivery in your case), the collector checks to see if the name in the config file matches any known exporter type. When I use your config file (with logdelivery defined) I get the error I shared above.

Here's the list of valid collector exporters: https://opentelemetry.io/ecosystem/registry/?s=exporter&component=&language=collector

If your exporter isn't found in this list then it's not a valid exporter. Do you see it anywhere in that list?

[vberegov]

I am using the Coralogix one .. and the config worked the way I posted it.

…

On Tue, Oct 10, 2023 at 12:46 PM Curtis Robert ***@***.***> wrote: Sorry for the confusion here. When an exporter is defined in the config file (logdelivery in your case), the collector checks to see if the name in the config file matches any known exporter type. When I use your config file (with logdelivery defined) I get the error I shared above. Here's the list of valid collector exporters: https://opentelemetry.io/ecosystem/registry/?s=exporter&component=&language=collector If your exporter isn't found in this list then it's not a valid exporter. Do you see it anywhere in that list? — Reply to this email directly, view it on GitHub <#27202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS24LQTAAWXCFLX2GCADTRLX6V3XVAVCNFSM6AAAAAA5HQJRIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJVHAZTSNBSHA> . You are receiving this because you were mentioned.Message ID: <open-telemetry/opentelemetry-collector-contrib/issues/27202/1755839428@ github.com>

-- Regards , Beregovsky Vadim

[github-actions]

Pinging code owners for exporter/coralogix: @povilasv @matej-g. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

The code owners have been pinged so hopefully you can get a response from them soon. If you need another option, you can try reaching out to support as mentioned in the README.

[povilasv]

Hey @vberegov , the config you reference doesn't seem correct, there is no logdelivery exporter, it should be coralogixexporter.

I've looked thru the changes between 0.83 and 0.85 and we have no PRs in coralogixexporter.

One thing you can try is adding logging exporter to your log pipeline and see if there are any messages coming in:

exporters:
  logging:
    verbosity: detailed
    sampling_initial: 5
    sampling_thereafter: 200

FYI for faster replies feel free to reach out to us via our in-app chat or by sending us an email to support@coralogix.com.

[crobert-1]

@vberegov Let us know if you have any other questions, or feel free to reach out to Coralogix support as @povilasv mentioned. I'll close this issue for now.