Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Service Logs streaming issue #34307

Closed
saiganeshkABI opened this issue Jul 30, 2024 · 4 comments
Closed

Azure Service Logs streaming issue #34307

saiganeshkABI opened this issue Jul 30, 2024 · 4 comments

Comments

@saiganeshkABI
Copy link

Component(s)

receiver/azureeventhub

What happened?

Description

The Azure service logs are unable to forward via OTel Collector.

Steps to Reproduce

Add the receiver component in builder config file
Run the builder
Configure Azure Event Hub receiver
Restart the otel collector
config.yaml

Expected Result

The logs should be streamed to the exporter

Actual Result

Getting issue while running the Otel Collector

Collector version

0.104.0

Environment information

Environment

OS: Windows
Compiler(if manually compiled): go 1.22.1

OpenTelemetry Collector configuration

receivers:
  azureeventhub:
    connection: Endpoint=$CONNECTION_STRING
exporters:
  datadog:
    api:
      key: "$API"
      site: "$SITE"
service:
  pipelines:
    logs:
      receivers: [otlp,azureeventhub]
      exporters: [datadog]

Log output

2024/07/30 08:15:47 collector server run finished with error: cannot start pipelines: *Error{Condition: amqp:link:stolen, Description: At least one receiver for the endpoint is created with epoch of '0', and so non-epoch receiver is not allowed. Either reconnect with a higher epoch, or make sure all epoch receivers are closed or disconnected. TrackingId:7e4c4ef7-c44e-4191-8b48-e761833ae1e2_B30, SystemTracker:datadogsecurity:eventhub:insights-activity-logs~8191, Timestamp:2024-07-30T08:15:47 Reference:bd89eaf1-314a-45f1-be80-63e298c7d01c, TrackingId:ee451c2a-f6d5-4d9e-acd8-a296660db2b5_B30, SystemTracker:datadogsecurity:eventhub:insights-activity-logs~8191|$default, Timestamp:2024-07-30T08:15:47 TrackingId:082ce81bf786443594531b6dfad80453_G1, SystemTracker:gateway5, Timestamp:2024-07-30T08:15:47, Info: map[]}

Additional context

No response

@saiganeshkABI saiganeshkABI added bug Something isn't working needs triage New item requiring triage labels Jul 30, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme
Copy link
Contributor

atoulme commented Jul 30, 2024

That doesn't seem like a problem with the receiver and more of an issue with your setup. Googling around for this error shows good results, you should check out this type of post: https://stackoverflow.com/questions/69075636/azure-eventhubs-throws-exception-at-least-one-receiver-for-the-endpoint-is-crea

@atoulme atoulme removed the needs triage New item requiring triage label Jul 30, 2024
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Sep 30, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants