PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001084PacketFenceloggingpublic2010-10-01 15:462012-06-14 12:47
Reporterobilodeau 
Assigned Toobilodeau 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionwon't fix 
PlatformOSOS Version
Product Version1.9.1 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001084: Add trigger type and trigger ID in violation.log
DescriptionThat'd be great to see the trigger type and ID in violation.conf so we have more info about the cause of the violation.
Right now we only have the violation ID.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-10-01 15:46rbalzardNew Issue
2010-10-01 15:46rbalzardStatusnew => assigned
2010-10-01 15:46rbalzardAssigned To => obilodeau
2010-11-19 14:24obilodeauTarget Version1.9.2 => 2.0.0
2010-11-19 14:41obilodeauCategory1.9.x => logging
2011-01-18 09:47obilodeauTarget Version2.0.0 => 2.0.1
2011-01-26 15:30obilodeauTarget Version2.0.1 => 2.0.2
2011-03-03 15:19obilodeauTarget Version2.0.2 => +1
2011-03-18 11:58fgaudreaultNote Added: 0001958
2011-10-25 10:24fgaudreaultNote Added: 0002395
2011-10-25 10:24fgaudreaultStatusassigned => resolved
2011-10-25 10:24fgaudreaultResolutionopen => won't fix
2011-11-21 12:05obilodeauReporterrbalzard => obilodeau
2011-11-21 12:05obilodeauTarget Version+1 =>
2012-06-14 12:47obilodeauStatusresolved => closed

Notes
(0001958)
fgaudreault   
2011-03-18 11:58   
I see no real benefits here... can you explain the use case?
(0002395)
fgaudreault   
2011-10-25 10:24   
Reopen if still interested in such feature.

The implementation of this would not be good in terms of time versus value.