https://signoz.io logo
Join Slack
Powered by
why isnt my otel-collector running awscloudwatch r...
# support
a
why isnt my otel-collector running awscloudwatch receiver? Im expecting it to pull cloud watch logs and then send them to Signoz
v
@nitya-signoz ^
n
can you check if the collector is pointed to the correct config ?
a
@nitya-signoz I will talk to you privately and share the whole config.yaml
It is using the right config.yaml
In the above image you can see the config.yaml location
it is the one which I added the cloudwatch receiver
I was able to show more logs and I can see that cloudwatch receiver is working! But why can't I see logs in Signoz?
my signoz instance has the following ports opened. Am I missing any other?
I was finally able to see logs in signoz
but something is not working properly in the cloudwatch receiver
This log group has logs from 02/04/2024, but the receiver is only considering newer logs, from today
why?
n
> I was able to show more logs and I can see that cloudwatch receiver is working! > But why can’t I see logs in Signoz? There are batch processors in your pipeline, so there will be some delay till you see them in signoz. Also you can play with the 
poll_interval
in your cloudwatch config. Yeah I think it just the receiver designed in that way ref :- https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/ff2b9d6eae9[…]a87db675340a89129d3e91a3/receiver/awscloudwatchreceiver/logs.go. I see that you have already created an issue in the upstream repo asking your question regarding why old logs are not collected, let’s wait for them to reply.
a
I left my ec2 running the collector and I still cant see all my logs from cloudwatch
kind weird
will wait the maintainers of the cloudwatch receiver to say something about it
5 Views
Open in Slack
PreviousNext
Powered by