Closed Bug 645895 Opened 13 years ago Closed 13 years ago

Logs from SUMO prod not going to cm-vpn01

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

All
Other
task
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jsocol, Assigned: dmoore)

Details

The logs from SUMO (in PHX) aren't making it to cm-vpn01. I assume this is just something that got overlooked in the move. If there's an equivalent cluster logging center in PHX, feel free to WONTFIX this, otherwise can we get that hooked back up?
Jeremy, how do we want to handle this?
Assignee: server-ops → jeremy.orem+bugs
Good question. We need a logging host that every server in phx can talk to over syslog.

Phong, can you you set this up and then assign to netops for firewall work. After that it can come back to me.


hostname: syslog1.webapp.phx1.mozilla.com.
Assignee: jeremy.orem+bugs → server-ops
Assignee: server-ops → phong
Would a VM work for this?
Let's give it a shot.
syslog1.webapp.phx1.mozilla.com is online.

oremj: can you tell net-ops what you need?
Assignee: phong → network-operations
Component: Server Operations → Server Operations: Netops
Sounds like we need to open up syslog to this host. Anything else?
Also, why is a datacenter-wide syslog server in the webapp vlan? Do we intend to send internal syslogs to this host, or only webserver logs?
Assignee: network-operations → dmoore
Chris, thoughts on this?
Going to kill this off.  Can't even tell if this made it into prod.

Centralized logging host shouldn't be on the webserver network.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.