关于“Introduction to Amazon Kinesis Firehose”的评价
正在加载…
未找到任何结果。

    关于“Introduction to Amazon Kinesis Firehose”的评价

    3842 条评价

    Matt C. · 已于 almost 8 years前审核

    Peter M. · 已于 almost 8 years前审核

    Dustin S. · 已于 almost 8 years前审核

    Archana S. · 已于 almost 8 years前审核

    sai krishna r. · 已于 almost 8 years前审核

    yuppppppppppppp

    omar s. · 已于 almost 8 years前审核

    Junho L. · 已于 almost 8 years前审核

    Ian M. · 已于 almost 8 years前审核

    Had problems with instructions - EC2 was unable to see mystream when only firehose created: 2016-12-17 20:48:32.849+0000 ip-10-0-0-112 (sender-11) com.amazon.kinesis.streaming.agent.tailing.AsyncPublisher [ERROR] AsyncPublisher[kinesis:mystream:/tmp/app.log*]:RecordBuffer(id=2,records=6,bytes=367) Retriable send error (com.amazonaws.services.kinesis.model.ResourceNotFoundException: Stream mystream under account 126546796233 not found. (Service: AmazonKinesis; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: de17e898-9705-a6da-8ed8-4e78e5cc7318)). Will retry. [ec2-user@ip-10-0-0-112 ~]$ aws firehose list-delivery-streams { "DeliveryStreamNames": [ "mystream" ], "HasMoreDeliveryStreams": false } [ec2-user@ip-10-0-0-112 ~]$ aws kinesis list-streams { "StreamNames": [] } Once I created a kinesis stream (not firehose) called mystream, it was able to send data but then the lab ended as I presume there is some plumbing between the two. [ec2-user@ip-10-0-0-112 ~]$ aws kinesis list-streams { "StreamNames": [ "mystream" ] } 2016-12-17 20:50:29.804+0000 ip-10-0-0-112 (FileTailer[fh:mystream:/tmp/app.log*].MetricsEmitter RUNNING) com.amazon.kinesis.streaming.agent.tailing.FileTailer [INFO] FileTailer[fh:mystream:/tmp/app.log*]: Tailer Progress: Tailer has parsed 6 records (264 bytes), transformed 0 records, skipped 0 records, and has successfully sent 6 records to destination. 2016-12-17 20:50:29.812+0000 ip-10-0-0-112 (Agent.MetricsEmitter RUNNING) com.amazon.kinesis.streaming.agent.Agent [INFO] Agent: Progress: 12 records parsed (968 bytes), and 6 records sent successfully to destinations. Uptime: 270059ms

    Brian S. · 已于 almost 8 years前审核

    Steve B. · 已于 almost 8 years前审核

    Foday C. · 已于 almost 8 years前审核

    Hong L. · 已于 almost 8 years前审核

    PPK file is not working. WHiel connecting from Putty getting error "Server refused key"

    Ramu V. · 已于 almost 8 years前审核

    3 stars

    ASHWINI C. · 已于 almost 8 years前审核

    Sajitha P. · 已于 almost 8 years前审核

    I couldn't find the Quries tab in the final step so couldn't complete the lab and see the stream coming through to Redshift.

    mike c. · 已于 almost 8 years前审核

    Jon A. · 已于 almost 8 years前审核

    Josh B. · 已于 almost 8 years前审核

    Ramon R. · 已于 almost 8 years前审核

    Pedro N. · 已于 almost 8 years前审核

    Liang F. · 已于 almost 8 years前审核

    could use an update (interface has changed some since this was written)

    Greg M. · 已于 almost 8 years前审核

    The tutorial skipped few important steps. Unable to select a Redshift cluster from drop down when creating a delivery stream.

    Vinaya Kumar B. · 已于 almost 8 years前审核

    Antonio I. · 已于 almost 8 years前审核

    Patrick G. · 已于 almost 8 years前审核

    我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。