Logs from SUMO prod not going to cm-vpn01

RESOLVED WONTFIX

Status

Infrastructure & Operations
NetOps
--
major
RESOLVED WONTFIX
7 years ago
5 years ago

People

(Reporter: jsocol, Assigned: dmoore)

Tracking

Details

(Reporter)

Description

7 years ago
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

Comment 2

7 years ago
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

Updated

7 years ago
Assignee: server-ops → phong

Comment 3

7 years ago
Would a VM work for this?

Comment 4

7 years ago
Let's give it a shot.

Comment 5

7 years ago
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
(Assignee)

Comment 6

7 years ago
Sounds like we need to open up syslog to this host. Anything else?
(Assignee)

Comment 7

7 years ago
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)

Updated

7 years ago
Assignee: network-operations → dmoore

Comment 8

7 years ago
Chris, thoughts on this?

Comment 9

7 years ago
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
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.