en	Save Failed. Remote Data Collectors in Sync Mode are not allowed to Save Rules. Save from the Main Cacti Server instead.

en	Please use an HTML Email Client

en	Cacti Syslog Threshold Alert '%s' for Host '%s'

en	Cacti Syslog Threshold Alert '%s'

en	Alert Name

en	Severity

en	Threshold

en	Count

en	Match String

en	Cacti Syslog Alert '%s' for Host '%s'

en	Cacti Syslog Alert '%s'

en	Hostname

en	Date

en	Level

en	Message

en	WARNING: A Syslog Threshold Alert has Been Triggered for Host '%s'

en	WARNING: A Syslog Threshold Alert has Been Triggered

en	Name:

en	Severity:

en	Threshold:

en	Count:

en	Message String:

en	Hostname:

en	Date:

en	Level:

en	Message:

en	, Host:

en	, URL:

en	Sev:

en	Event Alert - %s

en	, Count:

en	Host

en	Event Report - %s

en	Please rename either your config.php.dist or config_local.php.dist files in the syslog directory, and change setup your database before installing.

en	Syslog 2.0 Requires an Entire Reinstall. Please uninstall Syslog and Remove all Data before Installing. Migration is possible, but you must plan this in advance. No automatic migration is supported.

en	What upgrade/install type do you wish to use

en	When you have very large tables, performing a Truncate will be much quicker. If you are concerned about archive data, you can choose either Inline, which will freeze your browser for the period of this upgrade, or background, which will create a background process to bring your old syslog data from a backup table to the new syslog format. Again this process can take several hours.

en	Truncate Syslog Table

en	Inline Upgrade

en	Background Upgrade

en	Database Storage Engine

en	You have the option to make this a partitioned table by days.

en	MyISAM Storage

en	InnoDB Storage

en	Database Architecture

en	You have the option to make this a partitioned table by days. You can create multiple partitions per day.

en	Traditional Table

en	Partitioned Table

en	Retention Policy

en	Choose how many days of Syslog values you wish to maintain in the database.

en	Partitions per Day

en	Select the number of partitions per day that you wish to create.

en	%d Per Day

en	Upgrade

en	Install

en	Syslog %s Advisor

en	WARNING: Syslog Upgrade is Time Consuming!!!

en	The upgrade of the 'main' syslog table can be a very time consuming process. As such, it is recommended that you either reduce the size of your syslog table prior to upgrading, or choose the background option</p> <p>If you choose the background option, your legacy syslog table will be renamed, and a new syslog table will be created. Then, an upgrade process will be launched in the background. Again, this background process can quite a bit of time to complete. However, your data will be preserved</p> <p>Regardless of your choice, all existing removal and alert rules will be maintained during the upgrade process.</p> <p>Press <b>'Upgrade'</b> to proceed with the upgrade, or <b>'Cancel'</b> to return to the Plugins menu.

en	You can also select the retention duration. Please keep in mind that if you have several hosts logging to syslog, this table can become quite large. So, if not using partitioning, you might want to keep the size smaller.

en	You can also set the MySQL storage engine. If you have not tuned you system for InnoDB storage properties, it is strongly recommended that you utilize the MyISAM storage engine.

en	You have several options to choose from when installing Syslog. The first is the Database Architecture. You should elect to utilize Table Partitioning to prevent the size of the tables from becoming excessive thus slowing queries.

en	Syslog %s Settings

en	What uninstall method do you want to use?

en	When uninstalling syslog, you can remove everything, or only components, just in case you plan on re-installing in the future.

en	Remove Everything (Logs, Tables, Settings)

en	Syslog Data Only

en	Syslog Uninstall Preferences

en	Uninstall

en	Cancel

en	Syslog

en	General Settings

en	Syslog Enabled

en	If this checkbox is set, records will be transferred from the Syslog Incoming table to the main syslog table and Alerts and Reports will be enabled. Please keep in mind that if the system is disabled log entries will still accumulate into the Syslog Incoming table as this is defined by the rsyslog or syslog-ng process.

en	Enable Statistics Gathering

en	If this checkbox is set, statistics on where syslog messages are arriving from will be maintained. This statistical information can be used to render things such as heat maps.

en	Strip Domains

en	A comma delimited list of domains that you wish to remove from the syslog hostname, Examples would be 'mydomain.com, otherdomain.com'

en	Validate Hostnames

en	If this checkbox is set, all hostnames are validated. If the hostname is not valid. All records are assigned to a special host called 'invalidhost'. This setting can impact syslog processing time on large systems. Therefore, use of this setting should only be used when other means are not in place to prevent this from happening.

en	Refresh Interval

en	This is the time in seconds before the page refreshes.

en	Max Report Records

en	For Threshold based Alerts, what is the maximum number that you wish to show in the report. This is used to limit the size of the html log and Email.

en	%d Records

en	Command for Opening Tickets

en	This command will be executed for opening Help Desk Tickets. The command will be required to parse multiple input parameters as follows: --alert-name, --severity, --hostlist, --message. The hostlist will be a comma delimited list of hosts impacted by the alert.

en	HTML Notification Settings

en	Enable HTML Based Email

en	If this checkbox is set, all Emails will be sent in HTML format. Otherwise, Emails will be sent in plain text.

en	Format File to Use

en	Choose the custom html wrapper and CSS file to use. This file contains both html and CSS to wrap around your report. If it contains more than simply CSS, you need to place a special <REPORT> tag inside of the file. This format tag will be replaced by the report content. These files are located in the 'formats' directory.

en	Data Retention Settings

en	Syslog Retention

en	This is the number of days to keep events.

en	Syslog Alert Retention

en	This is the number of days to keep alert logs.

en	Remote Message Processing

en	Enable Remote Data Collector Message Processing

en	If your Remote Data Collectors have their own Syslog databases and process their messages independently, check this checkbox. By checking this Checkbox, your Remote Data Collectors will need to maintain their own 'config_local.php' file in order to inform Syslog to use an independent database for message display and processing. Please use the template file 'config_local.php.dist' for this purpose. WARNING: Syslog tables will be automatically created as soon as this option is enabled.

en	Remote Data Collector Rules Sync

en	If your Remote Data Collectors have their own Syslog databases and process thrie messages independently, check this checkbox if you wish the Main Cacti databases Alerts, Removal and Report rules to be sent to the Remote Cacti System.

en	Delete

en	Disable

en	Enable

en	Export

en	Indefinite

en	%d Day

en	%d Days

en	%d Week

en	%d Weeks

en	%d Month

en	%d Months

en	%d Year

en	Never

en	%d Minute

en	%d Minutes

en	Notice

en	Warning

en	Critical

en	Begins with

en	Contains

en	Ends with

en	Hostname is

en	Program is

en	Facility is

en	SQL Expression

en	Daily

en	Weekly

en	Import/Export

en	Alert Rules

en	Syslog Settings

en	Removal Rules

en	Report Rules

en	Normal User

en	System Administration

en	Syslog Removals

en	(Edit)

en	(Actions)

en	Syslog Alerts

en	Syslog Reports

en	Display Syslog in Range

en	There were %s Device records removed from the Syslog database

en	Syslog Utilities

en	Purge Syslog Devices

en	This menu pick provides a means to remove Devices that are no longer reporting into Cacti's syslog server.

en	Syslog Viewer

en	All Text

en	%d Chars

en	System Logs

en	Statistics

en	Alert Logs

en	Selected Alert

en	Syslog Alert View

en	Syslog Statistics Filter

en	Messages

en	Device Name

en	Facility

en	Priority

en	Program

en	Records

en	No Syslog Statistics Found

en	Device

en	All

en	None

en	Go

en	Clear

en	Search

en	Time Range

en	%d Hour

en	%d Hours

en	Entries

en	Default

en	[ Start: '%s' to End: '%s', Unprocessed Messages: %s ]

en	[ Unprocessed Messages: %s ]

en	Enter a search term

en	Select Device(s)

en	Devices Selected

en	All Devices Selected

en	Syslog Message Filter %s

en	Timespan

en	Custom

en	From

en	Start Date Selector

en	To

en	End Date Selector

en	Shift Time Backward

en	Define Shifting Interval

en	Shift Time Forward

en	Return filter values to their user defined defaults

en	Export Records to CSV

en	Save

en	Save Default Settings

en	Alerts

en	View Syslog Alert Rules

en	Removals

en	View Syslog Removal Rules

en	Reports

en	View Syslog Reports

en	Devices

en	Show All Devices

en	Show All Logs

en	Threshold Logs

en	Display Rows

en	Trim

en	Message Trim

en	Refresh

en	Facilities to filter on

en	All Facilities

en	Priority Levels

en	All Priorities

en	Emergency

en	Alert++

en	Alert

en	Critical++

en	Error++

en	Error

en	Warning++

en	Notice++

en	Info++

en	Info

en	Debug

en	Record Type

en	Removal Handling

en	All Records

en	Main Records

en	Removed Records

en	Informational

en	Actions

en	Unknown

en	No Syslog Messages

en	Alert Log Rows

en	Alert Removed

en	No Alert Log Messages

en	All Programs

en	Click 'Continue' to Delete the following Syslog Alert Rule(s).

en	Delete Syslog Alert Rule(s)

en	Click 'Continue' to Disable the following Syslog Alert Rule(s).

en	Disable Syslog Alert Rule(s)

en	Click 'Continue' to Enable the following Syslog Alert Rule(s).

en	Enable Syslog Alert Rule(s)

en	Click 'Continue' to Export the following Syslog Alert Rule(s).

en	Export Syslog Alert Rule(s)

en	Continue

en	The SQL Syntax Entered is invalid. Please correct your SQL.<br>

en	The Pre-processed SQL is:<br><br> %s

en	The processed SQL was invalid. Please correct your SQL

en	Not Set

en	1 Minute

en	1 Month

en	Alert Edit [edit: %s]

en	Alert Edit [new]

en	New Alert Rule

en	N/A

en	Details

en	Name

en	Please describe this Alert.

en	What is the Severity Level of this Alert?

en	Reporting Level

en	For recording Re-Alert Cycles, should the Alert be tracked at the System or Device level.

en	System

en	Reporting Method

en	Define how to Alert on the syslog messages.

en	Individual

en	For the 'Threshold' method, If the number seen is above this value an Alert will be triggered.

en	Match Type

en	Define how you would like this string matched. If using the SQL Expression type you may use any valid SQL expression to generate the alarm. Available fields include 'message', 'facility', 'priority', and 'host'.

en	Message Match String

en	Enter the matching component of the syslog message, the facility or host name, or the SQL where clause if using the SQL Expression Match Type.

en	Enabled

en	Is this Alert Enabled?

en	Disabled

en	Re-Alert Cycle

en	Do not resend this alert again for the same host, until this amount of time has elapsed. For threshold based alarms, this applies to all hosts.

en	Notes

en	Space for Notes on the Alert

en	Email Options

en	Notification List

en	Use the contents of this Notification List to dictate who should be notified and how.

en	Emails to Notify

en	Please enter a comma delimited list of Email addresses to inform. If you wish to send out Email to a recipient in SMS format, please prefix that recipient's Email address with 'sms@'. For example, if the recipients SMS address is '2485551212@mycarrier.net', you would enter it as 'sms@2485551212@mycarrier.net' and it will be formatted as an SMS message.

en	Email Body Text

en	This information will appear in the body of the Alert just before the Alert details.

en	Open Ticket

en	Should a Help Desk Ticket be opened for this Alert. NOTE: The Ticket command script will be populated with several 'ALERT_' environment variables for convenience.

en	No

en	Yes

en	Command

en	When an Alert is triggered, run the following command. The following replacement variables are available '<HOSTNAME>', '<ALERTID>', '<MESSAGE>', '<FACILITY>', '<PRIORITY>', '<SEVERITY>'. Please note that '<HOSTNAME>' is only available on individual thresholds. These replacement values can appear on the command line, or be gathered from the environment of the script. When used from the environment, those variables will be prefixed with 'ALERT_'.

en	Rows

en	Import

en	Syslog Alert Filters

en	Method

en	Threshold Count

en	Search String

en	Email Addresses

en	Last Modified

en	By User

en	Multiple

en	No Syslog Alerts Defined

en	Import Alert Rule from Local File

en	If the XML file containing the Alert Rule definition data is located on your local machine, select it here.

en	Import Alert Rule from Text

en	If you have the XML file containing the Alert Ruledefinition data as text, you can paste it into this box to import it.

en	Import Alert Rule

en	Imported

en	NOTE: Alert '%s' %s!

en	Updated

en	ERROR: Alert '%s' %s Failed!

en	Update

en	Reprocess

en	Click 'Continue' to Delete the following Syslog Removal Rule(s).

en	Delete Syslog Removal Rule(s)

en	Click 'Continue' to Disable the following Syslog Removal Rule(s).

en	Disable Syslog Removal Rule(s)

en	Click 'Continue' to Enable the following Syslog Removal Rule(s).

en	Enable Syslog Removal Rule(s)

en	Click 'Continue' to Re-process the following Syslog Removal Rule(s).

en	Retroactively Process Syslog Removal Rule(s)

en	Click 'Continue' to Export the following Syslog Removal Rule(s).

en	Export Syslog Removal Rule(s)

en	Rule '%s' resulted in %s/%s messages removed/transferred

en	Removal Rule Edit [edit: %s]

en	Removal Rule Edit [new]

en	New Removal Record

en	New Removal Rule

en	Removal Rule Details

en	Removal Rule Name

en	Please describe this Removal Rule.

en	Enabled?

en	Is this Removal Rule Enabled?

en	String Match Type

en	Syslog Message Match String

en	Method of Removal

en	Deletion

en	Transferal

en	Removal Rule Notes

en	Space for Notes on the Removal rule

en	Rules

en	Syslog Removal Rule Filters

en	Removal Name

en	Transfer

en	No Syslog Removal Rules Defined

en	Import Removal Rule from Local File

en	If the XML file containing the Removal Rule definition data is located on your local machine, select it here.

en	Import Removal Rule from Text

en	If you have the XML file containing the Removal Rule definition data as text, you can paste it into this box to import it.

en	Import Removal Rule

en	NOTE: Removal Rule '%s' %s!

en	ERROR: Removal Rule '%s' %s Failed!

en	Click 'Continue' to Delete the following Syslog Report(s).

en	Delete Syslog Report(s)

en	Click 'Continue' to Disable the following Syslog Report(s).

en	Disable Syslog Report(s)

en	Click 'Continue' to Enable the following Syslog Report(s).

en	Enable Syslog Report(s)

en	Click 'Continue' to Export the following Syslog Report Rule(s).

en	Export Syslog Report Rule(s)

en	You must select at least one Syslog Report.

en	Return

en	Report Edit [edit: %s]

en	Report Edit [new]

en	New Report Record

en	Please describe this Report.

en	Is this Report Enabled?

en	Define how you would like this string matched.

en	The matching component of the syslog message.

en	Frequency

en	How often should this Report be sent to the distribution list?

en	Send Time

en	What time of day should this report be sent?

en	Report Format

en	The information that will be contained in the body of the Report.

en	Comma delimited list of Email addresses to send the report to.

en	Space for Notes on the Report

en	Syslog Report Filters

en	Report Name

en	Last Sent

en	No Syslog Reports Defined

en	Import Report Rule from Local File

en	If the XML file containing the Report Rule definition data is located on your local machine, select it here.

en	Import Report Rule from Text

en	If you have the XML file containing the Report Rule definition data as text, you can paste it into this box to import it.

en	Import Report Data

en	NOTE: Report Rule '%s' %s!

en	ERROR: Report Rule '%s' %s Failed!