Skip to content
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.

Cloud watch logs are not read #83

Open
RajezMariner opened this issue Jan 23, 2020 · 2 comments
Open

Cloud watch logs are not read #83

RajezMariner opened this issue Jan 23, 2020 · 2 comments

Comments

@RajezMariner
Copy link

Hi Team,

Below is the setting I have mentioned in my pipeline config. I am not able to fetch the aws cloud watch logs though. Not sure what I am missing. I have specified the correct access id and secret key. Also the logs group name is correct. Not sure what I am missing from the config perspective. Do we need to install any other beat shippers for this?

input {
	cloudwatch_logs {
		id => "cloudwatchid"
                log_group => "log group ID"
                access_key_id => ""
                secret_access_key => ""
		log_group_prefix => true
         }
}

filter {
}

output {
	elasticsearch {
		id => "elastic-search-id"
		hosts => "elasticsearch:9200"
		user => "elastic"
		password => "changeme"
	}
}

Thanks,
Rajesh

@RajezMariner
Copy link
Author

I could see the outputs are printed in the logstash stdout. But in Kibana , how to retrieve the elastic search? Is that a indices problem?

@RollingFred
Copy link

You should probably provide an index in your output configuration. Look there:
https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants