tyler.durden/pandorafms
1
0
Fork 0
mirror of https://github.com/pandorafms/pandorafms.git synced 2025-07-28 16:24:54 +02:00
Code Issues Packages Projects Releases Wiki Activity

Added new events response macros documentation

Browse Source
This commit is contained in:
fermin831 2017-11-20 15:06:20 +01:00
parent 2425d19ddd
commit f021664336
2 changed files with 60 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
pandora_console/include/help/en/help_response_macros.php
View File

@ -5,27 +5,52 @@
?>Event responses macros</h1> ?>Event responses macros</h1>
<p> <p>
The response target (command or URL) accepts macros to custom it. The response target (command or URL) accepts macros to customize it.
<br><br> <br><br>
The macros accepted are the following: The accepted macros are:
<ul> <ul>
<li><b>Agent address:</b> _agent_address_</li> <li><b>Agent address:</b> _agent_address_</li>
<li><b>Agent id:</b> _agent_id_</li> <li><b>Agent ID:</b> _agent_id_</li>
<li><b>Event id:</b> _event_id_</li> <li><b>Event related alert ID:</b> _alert_id_</li>
<li><b>Date on which the event occurred:</b> _event_date_</li>
<li><b>Extra ID:</b> _event_extra_id_</li>
<li><b>Event ID:</b> _event_id_</li>
<li><b>Event instructions:</b> _event_instruction_</li>
<li><b>Event severity ID:</b> _event_severity_id_</li>
<li><b>Event severity (translated by Pandora console):</b> _event_severity_text_</li>
<li><b>Event source:</b> _event_source_</li>
<li><b>Event status (new, validated or event in process):</b> _event_status_</li>
<li><b>Event tags separated by commas:</b> _event_tags_</li>
<li><b>Full text of the event:</b> _event_text_</li>
<li><b>Event type (System, going into Unknown Status...):</b> _event_type_</li>
<li><b>Date on which the event occurred in utimestamp format:</b> _event_utimestamp_</li>
<li><b>Group ID:</b> _group_id_</li>
<li><b>Group name in database:</b> _group_name_</li>
<li><b>Event associated module address:</b> _module_address_</li>
<li><b>Event associated module ID:</b> _module_id_</li>
<li><b>Event associated module name:</b> _module_name_</li>
<li><b>Event owner user:</b> _owner_user_</li>
<li><b>User ID:</b> _user_id_</li>
</ul> </ul>
<h4>Custom fields</h4>
Custom event fields are also available in event response macros. They would
have <b>_customdata_*_</b> form where the asterisk (*) would have to be
replaced by the custom field key you want to use.
<h3>Basic use</h3> <h3>Basic use</h3>
In example, to ping the agent associated to the event: For example, to ping the agent associated with the event:
<br><br> <br><br>
Configure command like: <i>ping -c 5 _agent_address_</i> Configure the command as follows: <i>ping -c 5 _agent_address_</i>
<br><br> <br><br>
If there are configured parameters, is possible use it as macros too. If there are configured parameters, it is possible to use them as macros, too.
<h3>Parameters macros</h3> <h3>Parameters macros</h3>
In example, to custom a URL with parameters: For example, to customize a URL with parameters:
<br><br> <br><br>
Configure parameters like: <i>User,Section</i> Configure the parameters as follows: <i>User,Section</i>
<br><br> <br><br>
And configure the URL like: <i>http://example.com/index.php?user=_User_&amp;section=_Section_</i> And configure the URL like this: <i>http://example.com/index.php?user=_User_&amp;section=_Section_</i>
</p> </p>

25
pandora_console/include/help/ja/help_response_macros.php
View File

@ -12,9 +12,34 @@
<ul> <ul>
<li><b>エージェントアドレス:</b> _agent_address_</li> <li><b>エージェントアドレス:</b> _agent_address_</li>
<li><b>エージェントID:</b> _agent_id_</li> <li><b>エージェントID:</b> _agent_id_</li>
<li><b>Event related alert ID:</b> _alert_id_</li>
<li><b>Date on which the event occurred:</b> _event_date_</li>
<li><b>Extra ID:</b> _event_extra_id_</li>
<li><b>イベントID:</b> _event_id_</li> <li><b>イベントID:</b> _event_id_</li>
<li><b>Event instructions:</b> _event_instruction_</li>
<li><b>Event severity ID:</b> _event_severity_id_</li>
<li><b>Event severity (translated by Pandora console):</b> _event_severity_text_</li>
<li><b>Event source:</b> _event_source_</li>
<li><b>Event status (new, validated or event in process):</b> _event_status_</li>
<li><b>Event tags separated by commas:</b> _event_tags_</li>
<li><b>Full text of the event:</b> _event_text_</li>
<li><b>Event type (System, going into Unknown Status...):</b> _event_type_</li>
<li><b>Date on which the event occurred in utimestamp format:</b> _event_utimestamp_</li>
<li><b>Group ID:</b> _group_id_</li>
<li><b>Group name in database:</b> _group_name_</li>
<li><b>Event associated module address:</b> _module_address_</li>
<li><b>Event associated module ID:</b> _module_id_</li>
<li><b>Event associated module name:</b> _module_name_</li>
<li><b>Event owner user:</b> _owner_user_</li>
<li><b>User ID:</b> _user_id_</li>
</ul> </ul>
<h4>Custom fields</h4>
Custom event fields are also available in event response macros. They would
have <b>_customdata_*_</b> form where the asterisk (*) would have to be
replaced by the custom field key you want to use.
<h3>基本的な利用方法</h3> <h3>基本的な利用方法</h3>
例として、イベントに関連付けしたエージェントへの ping を示します。 例として、イベントに関連付けしたエージェントへの ping を示します。
<br><br> <br><br>