It is possible to integrate logs into Logsign with syslog from the Vcenter system.
Integrations to be made on Vmware are as follows;
1- Go to VMware Appliance Management
2- It must be logged with an authorized user, preferably the root user created for appliance management can be used.
3- Go to Syslog tab.
4- In the Configuration tab, the Logsign IP is defined.
5- When checked after this stage, it is seen that the logs are sent with "send test message".
After performing the configurations on the Vmware, you'll complete the addition of the Logsign Unified SecOps Platform as a source.
Open the Logsign Unified SecOps Platform WEB interface and click on the "+ Device" button under the Data Collection tab, which is then clicked on the Settings tab in the menu bar on the top of the page. On the page that opens, click Syslog -> Vmware ->vCenter. Then, on the incoming page, fill in the information for the Vmware vCenter.
Host: IP address information of the Vmware vCenter that you want to retrieve the logs.
Encoding: utf_8, which is accepted as the general standard in Information Technologies, is set as default. Agree in the same way.
Offset: To explain it in terms of definition, let's say "time difference." If the "system" time you want to log in is forward or backward from the real-time difference, you can edit it accordingly. The symbol "+" moves forward, and "-" moves backward. Time information is specified in minutes.
Data Policy: You can filter in or out of incoming data. In the Data Policy section, you can specify the kind of logs (word, event movement type, etc.) that you want to receive or not from the source. Our default setting here is the Default Policy, which has the default rule is "collect all logs."
Max Line Length to Process: Each log is generated as a single line. So, the Logsign Unified SecOps Platform takes these logs and analyzes them. In some cases, the number of characters in a single line of a single log file can be more significant than two thousand forty-eight (2048). In such cases, you can change this part.
Check Health: If you tick this box, that will inform you about the service and operability of the Logsign.
The Health Check Period tab will come up when you tick the box. This part is the time interval information to be checked.
Device Name: You must enter a descriptive name according to the configuration you are making (For ex., vCenter). It can provide convenience for people who analyze logs. You can think of the Description field as a resource-specific area.
Tag: Slightly different from the Description section, it can be used for a broader purpose. For example, you can query by tag; and make tag-based definitions while creating a report. Define each tag as vcenter1 or vcenter2. If you want to query about an event, you will get a shorter result when you search according to vcenter1 name.
Click on the Save button to save the integration.
Sending vCenter Logs Through a Syslog Relay
We recommend that vCenter sends its logs directly to Logsign. vCenter sends syslog in RFC 5424 format, and the vCenter parser reads this format.
Some environments forward vCenter logs through an intermediate syslog server (relay), for example to filter logs. Some relays rewrite the RFC 5424 header as an RFC 3164 header. In Logsign versions that include the RFC 3164 relay update for the vCenter parser, the parser also reads these lines. Check the Release Notes for the version that includes this update.
The parser reads a relayed line when it has this form:
Mmm dd HH:MM:SS <host> <tag>[<pid>] <original vCenter message>
- The tag is followed by a space, not by a colon. The
[<pid>]part is optional. - The original vCenter message after the tag must stay unchanged.
- Lines that the relay produces for itself in the
tag[pid]: messageform are not vCenter events. The vCenter parser does not parse them.
An RFC 3164 timestamp has no year and no time zone. Logsign adds the current year to the timestamp. If a timestamp is more than one day in the future, Logsign uses the previous year (for example, December logs that arrive in January). If the event times of relayed logs look shifted, use the Offset field to correct them.
If you can change the relay configuration, forward the logs in RFC 5424 format. For rsyslog, the template is RSYSLOG_SyslogProtocol23Format.