Closed
Bug 1139617
Opened 10 years ago
Closed 10 years ago
Set up Heka instance to route Telemetry data from prod to dev IAM for demo use
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rmiller, Assigned: whd)
References
Details
We'd like to pipe a subset of the Telemetry data to the demo Heka instance living in the Cloud Services Dev IAM. Exposing Kafka across IAMs is difficult, so we want to use a stand-alone Heka instance in the Prod IAM that will pull data from Kafka and use a TcpOutput to push the records directly to the Heka demo box.
Assignee | ||
Comment 1•10 years ago
|
||
https://github.com/mozilla-services/puppet-config/pull/1150
https://github.com/mozilla-services/svcops/pull/422
https://pipeline-prototype-forwarder.prod.mozaws.net/
https://pipeline-prototype-cep.dev.mozaws.net/
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•