Node Event logs are only available via the UI

Bug #1391228 reported by Jason Hobbs on 2014-11-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
ubuntudotcom1

Bug Description

The node event log is great and is helpful for debugging issues, but it's only available via the UI.

I think it should be available as log files on the filesystem and/or API too so it's easy to include in tar balls of /var/log/maas.

Related branches

summary: - Node Event logs should be available as files
+ Node Event logs are only available via the UI
description: updated
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
tags: added: log
Christian Reis (kiko) on 2014-11-11
Changed in maas:
milestone: none → next
Jason Hobbs (jason-hobbs) wrote :

We need to collect this information to triage OIL failures automatically. Can the priority on getting this added to the API be bumped?

tags: added: oil
Gavin Panella (allenap) on 2015-03-10
Changed in maas:
importance: Medium → High
Jason Hobbs (jason-hobbs) wrote :

A little extra info on our use case. When we hit a failure in MAAS that has to do with a node deploying properly we want to collect information about that deployment.

We'd like to be able to retrieve the logs related to the last attempted deployment of a node, not a node's entire event log, as our event logs have thousands of events per nodes. We could do this with a time range query if MAAS's timestamps match our OIL systems' (which they should), or if we could retrieve a "current event id" before deployment and then retrieve all events after that when a deployment fails, that would work too.

Changed in maas:
status: Triaged → Fix Committed
assignee: nobody → ubuntudotcom1 (ubuntudotcom1)
Changed in maas:
status: Fix Committed → Fix Released
milestone: next → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers