Make all ticket parameters possible (cluster-wide) #1
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: LotusGuild/hwmonDaemon#1
Reference in New Issue
Block a user
Ticket Parameters
Hostname [hostname] (e.g., [medium1], [medium2], [pbs]) or [proxmox-cluster]
Action Type [manual], [auto]
Issue Type [hardware], [network], [power], [software], [security], [configuration], [maintenance], [upgrade]
Scope [single-node], [cluster-wide], [external-impact]
Environment [production], [testing], [development]
Type [maintenance], [upgrade], [new-install]
Example Ticket Title, please put tags in this order always
[medium1][manual][hardware] SHORT DESCRIPTION OF ISSUE [cluster-wide][production][maintenance]
Not title Tags but needed info for the ticket
P1 - Critical Impact
P2 - High Impact
P3 - Medium Impact
P4 - Low Impact
Hardware
Software
Network
Security
Other
Incident
Request
Problem
Task
Implemented. Cluster-wide tickets are fully supported: cluster-scoped issues (e.g. Ceph health) use the cluster name as the source, carry the [cluster-wide] scope tag, and deduplicate across all nodes (hostname excluded from the dedup hash). The daemon emits titles in the exact tag order from the example above — [source][action][issue_tag] description [scope][environment][type] — as seen on live tickets like [monitor-02][auto][hardware] … [single-node][production][problem]. Action (auto/manual), scope (single-node/cluster-wide), and the issue/problem/task/maintenance/upgrade types are all in place. The only enum values from the original taxonomy not yet wired up are ones the daemon never generates (power/security/configuration issue tags, external-impact scope, testing/development environments); those can be added if a future non-hardware/non-production source needs them. Closing as done.