com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html' is unknown.
SUSE
Background
The Linux for SUSE Servers logs analysis App automatically Collect - Read - Parse - Analyzes - Reports all machine generated log data of the server and presents a comprehensive set of graphs and reports to analyze machine generated data. Use a predefined set of dashboards and gadgets to visualize and address the system software, code written, and infrastructure during development, testing, and production. This Linux for SUSE logs analysis App helps measure, troubleshoot, and optimize your servers integrity, stability and quality with the several visualization and investigation dashboards.
Steps:
- The Linux App for SUSE is running on messages, secure, mail, kern and cron standard logs.
When adding/editing the logs to XpoLog it is mandatory to apply the correct log type(s) to each of the logs:- suse - all logs that the application will analyze must have suse as a log type.
- linux - all logs that the application will analyze must have linux as a log type.
- messages - only the messages logs must also be configured to have messages as a log type.
- warn- only the auth/secure logs must also be configured to have warn as a log type.
- mail - only the mail log must also be configured to have mail as a log type.
- suse - all logs that the application will analyze must have suse as a log type.
- Once the required information is set, on each log click next and edit the log pattern, this step is crucial to the accuracy and deployment of the Linux App. Use the following patterns for each of the logs:
- SUSE messages log:
First Pattern:
{date:Date,yyyy-MM-dd'T'HH:mm:ss.SSSSSS;yyyy-MM-dd HH:mm:ss.SSS}{text:timezone} {text:source,ftype=source} kernel: [{text:time-taken,ftype=time-taken;,}] {text:Message,ftype=message}
Second Pattern:
{date:Date,yyyy-MM-dd'T'HH:mm:ss.SSSSSS;yyyy-MM-dd HH:mm:ss.SSS}{text:timezone} {text:Server,ftype=server} {text:Process,ftype=process}{block,start,emptiness=true}[{text:pid,ftype=pid}]{block,end,emptiness=true}: {text:Message,ftype=message} - SUSE warn log:
First Pattern:
{date:Date,yyyy-MM-dd'T'HH:mm:ss.SSSSSS;yyyy-MM-dd HH:mm:ss.SSS}{text:timezone} {text:source,ftype=source} kernel: [{text:time-taken,ftype=time-taken;,}] {text:Message,ftype=message}
Second Pattern:
{date:Date,yyyy-MM-dd'T'HH:mm:ss.SSSSSS;yyyy-MM-dd HH:mm:ss.SSS}{text:timezone} {text:Server,ftype=server;,} {text:Process,ftype=process;,}{block,start,emptiness=true}[{text:pid,ftype=pid;,}]{block,end,emptiness=true}: {text:Message,ftype=message;,} - SUSE mail log:
{date:Date,yyyy-MM-dd'T'HH:mm:ss.SSSSSS;yyyy-MM-dd HH:mm:ss.SSS}{text:timezone}Â {text:source} {text:process name,ftype=process;,}{block,start,emptiness=true}[{number:process id}]{block,end,emptiness=true}: {regexp:session,refName=Message;ftype=session,^(\w+):}{regexp:From,refName=Message;ftype=from,\s+from=([^,]+)}{regexp:To,refName=Message;ftype=to,\s+to=([^,]+)}{text:Message,ftype=message;,}
- SUSE messages log: