Set up dev logstash / statsd server for metlog dev and testing usage

RESOLVED FIXED

Status

P2
critical
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: RaFromBRC, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

7 years ago
We're making good progress on the services metrics logging stuff, and are ready to start testing things in a more production-like environment.  To this end, we'd like a stable(-ish) dev installation of logstash and statsd set up so we can start pushing messages through and watching them end up in the right destinations.  A stable IP address so we can start to explicitly allow connections to services provided by the metrics team would be helpful.  And extra credit if we can get a sentry installation too.
(Reporter)

Comment 1

7 years ago
Just bumping this to make sure it doesn't fall off the radar.  :)
Severity: normal → blocker
Priority: -- → P2
(In reply to Rob Miller [:RaFromBRC :rmiller] from comment #0)
> We're making good progress on the services metrics logging stuff, and are
> ready to start testing things in a more production-like environment.  To
> this end, we'd like a stable(-ish) dev installation of logstash and statsd
> set up so we can start pushing messages through and watching them end up in
> the right destinations.

I have logstash installed on dev sync webheads: sync[1-6].web.mtv1.dev.svc.mozilla.com (sync4 is currently sick). It's currently setup to run through daemontools (/service/logstash). Once you put a config file there (/etc/logstash.conf) you can turn on the service by running "sudo svc -u /service/logstash". stdout & stderr will be in /service/logstash/log/main/current.

statsd is also installed, pushing to a metrics stream on mon1.mtv1.dev.

> A stable IP address so we can start to explicitly
> allow connections to services provided by the metrics team would be helpful.

dev environment lives in 10.250.64.0/22

> And extra credit if we can get a sentry installation too.

Could you turn this into a separate bug?
Severity: blocker → critical
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Whiteboard: [qa+]
You need to log in before you can comment on or make changes to this bug.