Azure / Azure/azure-diagnostics-tools
azureblob - not getting any data pulled out
- Dominant language
- Ruby
- Stars
- 101
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We have stored file (sample text file) in Azure blob under demo container.
We have follow the instruction from [here](https://github.com/Azure/azure-diagnostics-tools/tree/master/Logstash/logstash-input-azureblob).
I am getting below logs only and not getting any content from azureblob:
`D:\logstash-6.6.2>bin\logstash -f azureblobconfig.conf
Sending Logstash logs to D:/logstash-6.6.2/logs which is now configured via log4j2.properties
[2019-04-02T13:46:31,695][WARN ][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
[2019-04-02T13:46:31,726][INFO ][logstash.runner ] Starting Logstash {"logstash.version"=>"6.6.2"}
[2019-04-02T13:46:43,002][INFO ][logstash.inputs.logstashinputazureblob] Using version 0.9.x input plugin 'azureblob'. This plugin should work but would benefit from use
by folks like you. Please let us know if you find bugs or have suggestions on how to improve this plugin.
[2019-04-02T13:46:44,139][INFO ][logstash.pipeline ] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.de
lay"=>50}
[2019-04-02T13:46:48,822][INFO ][logstash.pipeline ] Pipeline started successfully {:pipeline_id=>"main", :thread=>"#"}
[2019-04-02T13:46:48,869][INFO ][logstash.agent ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}
[2019-04-02T13:46:49,963][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600}`
Below is my configuration:
`input
{
azureblob
{
storage_account_name => "account_name"
storage_access_key => "key"
container => "demo"
registry_create_policy => "start_over"
}
}
output {
stdout { codec => rubydebug }
} `
Please let me know if i am missing anything here.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.