Sending flow messages from contrail-vrouter-agent to syslog
contrail-
Under the section DEFAULT:
log_flow=1 - This enables logging of all flow messages
use_syslog=1 - This enables sending of all messages including flow messages to syslog
syslog_
log_level=SYS_INFO - This will change the logging level of contrail-
If syslog is enabled then flow messages will NOT be sent to Contrail Analytics. The destinations are mutually exclusive.
Flow log sampling settings apply the same regardless of the flow log destination specified. If sampling is enabled then syslog messages will be sampled using the same rules that would apply to Contrail Analytics. If non-sampled flow data is required then sampling must be disabled via configuration settings.
Flow events for termination will include both appropriate teardown fields and appreciate setup fields.
The flow messages will be sent to syslog using a severity of INFO
User can then configure rsyslog on the compute node to send syslog messages with facility LOCAL0 , severity INFO and below to remote syslog server and higher severity messages can be logged to local file to allow for debugging.
The flow messages will appear in syslog in a format similar to below log:
May 24 14:40:13 a7s10 contrail-
Note that several individual flow messages may be packed into a single syslog message for improved efficiency.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Walter Barnes
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for r3.1
- Implementation:
- Implemented
- Milestone target:
- r3.1.0.0-fcs
- Started by
- Raj Reddy
- Completed by
- Raj Reddy