Closed Bug 1305042 Opened 9 years ago Closed 9 years ago

ATMO V2: logs should be accessible through a unique interface

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mdoglio, Unassigned)

References

Details

(Whiteboard: [SvcOps])

The only way I have to check the logs at the moment is to: 1)ssh into the bastion machine 2)query the aws ec2 api from the command line to get the list of available nodes 3)choose randomly one of them and ssh into 4)inspecting the logs using `journalctl -u docker-atmo-app` 5)(if I didn't find what I was looking for) go back to 3) and keep iterating Is it possible to have a unique interface where I can see all the logs? Bonus points if I don't have to ssh into any machine to do that
Something similar to https://papertrailapp.com/ would be ideal if compatible with the underlying infrastructure.
Blocks: 1305065
Whiteboard: [SvcOps]
Priority: -- → P2
Summary: http://atmo.dev.mozaws.net logs should be accessible through a unique interface → ATMO V2: http://atmo.dev.mozaws.net logs should be accessible through a unique interface
Summary: ATMO V2: http://atmo.dev.mozaws.net logs should be accessible through a unique interface → ATMO V2: logs should be accessible through a unique interface
This is fixed now by using Papertrail for the Heroku based version of ATMO
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.