04-show_file-documentCreated with Sketch.07-revisions_historyCreated with Sketch. 08-backlink_link-variantCreated with Sketch.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
en:documentation:01_understanding:01_introduction [2021/05/19 13:15]
127.0.0.1 editor externo 		en:documentation:01_understanding:01_introduction [2023/02/20 16:54] (current)
Line 47: Line 47:
 The company financing and coordinating all the back up work on Pandora FMS's development is Artica ST, a Spanish company, founded in 2005 by the creator of Pandora FMS. The company financing and coordinating all the back up work on Pandora FMS's development is Artica ST, a Spanish company, founded in 2005 by the creator of Pandora FMS.
  
-{{  :wiki:roadmap_2017.png?850  }}+{{  :wiki:pfms-roadmap-2021.png  }}
  
 Pandora FMS can be found to this day among Sourceforge’s top rated, with thousands of downloads and satisfied users all over the world. For more information on Pandora FMS's evolution and to see a road map of the project, please visit [[http://pandorafms.com|http://pandorafms.com]] Pandora FMS can be found to this day among Sourceforge’s top rated, with thousands of downloads and satisfied users all over the world. For more information on Pandora FMS's evolution and to see a road map of the project, please visit [[http://pandorafms.com|http://pandorafms.com]]
 +
  
 ==== A Quick Glance at Pandora FMS features ==== ==== A Quick Glance at Pandora FMS features ====
Line 88: Line 89:
 Remote monitoring means that Pandora FMS’s server probes, ('polling') in a **synchronous**  way, the devices it intends to monitor. Remote Monitoring does not refe to the 'local' monitoring, based on agents installed on the devices to be observed. Remote monitoring means that Pandora FMS’s server probes, ('polling') in a **synchronous**  way, the devices it intends to monitor. Remote Monitoring does not refe to the 'local' monitoring, based on agents installed on the devices to be observed.
  
-{{  :wiki:esquema-remote-module-execution.png?500  }}+{{  :wiki:esquema-remote-module-execution.png  }}
  
 Generally speaking, remote monitoring is done with two different purposes: Generally speaking, remote monitoring is done with two different purposes:
Line 126: Line 127:
 According to the nomenclature used by Pandora FMS, ‘agent’ is used to refer to the entity containing the information and ‘software agent’ as the part of that software installed in that system to retrieve information and report back to Pandora FMS server. The software agent is executed constantly in the system (as a service) and reports information periodically. According to the nomenclature used by Pandora FMS, ‘agent’ is used to refer to the entity containing the information and ‘software agent’ as the part of that software installed in that system to retrieve information and report back to Pandora FMS server. The software agent is executed constantly in the system (as a service) and reports information periodically.
  
-{{  :wiki:esquema-agent-module-execution.png?500  }}+{{  :wiki:esquema-agent-module-execution.png  }}
  
 The agents allow to do more than obtain information through commands, for example to obtain inventory information. Agents can also be configured to react in case of a problem or a failure, interacting automatically with the system, deleting a temporary file or executing a given command. The agents allow to do more than obtain information through commands, for example to obtain inventory information. Agents can also be configured to react in case of a problem or a failure, interacting automatically with the system, deleting a temporary file or executing a given command.
Line 138: Line 139:
 Before starting deploying, is is important to set the key points of the technological platform to be monitored. That way, before having information about specific data on the systems, it is clear what it is for and how to make full use of it without wasting time on researches or trivial things. Before starting deploying, is is important to set the key points of the technological platform to be monitored. That way, before having information about specific data on the systems, it is clear what it is for and how to make full use of it without wasting time on researches or trivial things.
  
-{{  :wiki:ciclo_monitorizacion.png?400  }}+{{  :wiki:ciclo_monitorizacion.png  }}
  
 In your case, what do you think describes your monitoring needs better? In your case, what do you think describes your monitoring needs better?
Line 162: Line 163:
 In order to be able to draw up action procedures, it will be necessary to take into account several factors: In order to be able to draw up action procedures, it will be necessary to take into account several factors:
  
-***Urgency of the event**: being able to distinguish something normal from something rare or critical. ***Form of notification**: email, sms, Telegram, sound alert… ***Scaling**: different forms of warning in face of a recurrent problem. A common case is notification to a manager after a certain amount of time without solving a problem. +***Urgency of the event**: being able to distinguish something normal from something rare or critical. ***Form of notification**: email, sms, Telegram, sound alert… ***Scaling**: different forms of warning in face of a recurrent problem. A common case is notification to a manager after a certain amount of time without solving a problem. Before entering any configuration, it is advisable to have these concepts clear, draw up schemes with the critical elements, how to monitor them, what to do with all the information gathered and how to report problems that arise. {{  :wiki:scalation_example.png?500  }}By focusing on the most critical issues first, you reach a logical starting point that defines **what**  the most important issues for your organization are. Once you know what the most critical elements are, you can define **how**  to monitor the target(s), while considering **who**  will be responsible for the resolution of the reported problems in those systems as well as how to notify the appropriate people of the existence of a problem.
-Before entering any configuration, it is advisable to have these concepts clear, draw up schemes with the critical elements, how to monitor them, what to do with all the information gathered and how to report problems that arise. +
- +
-{{  :wiki:scalation_example.png?500  }} +
- +
-By focusing on the most critical issues first, you reach a logical starting point that defines **what**  the most important issues for your organization are. Once you know what the most critical elements are, you can define **how**  to monitor the target(s), while considering **who**  will be responsible for the resolution of the reported problems in those systems as well as how to notify the appropriate people of the existence of a problem. +
 ==== Supervision Models ==== ==== Supervision Models ====
  
 By supervision models, we are stating that a monitoring system is designed to report information and work automatically, but this is supervised by a human being in a direct or indirect way. This person often receives the title of //operator//, which is the person who looks at the screen or otherwise receives the events, whether it might be by means of a smartphone device or similar, by e-mail or logs registered with another tool. The "how" does not matter, the important thing is the fact that someone is minding the system. By supervision models, we are stating that a monitoring system is designed to report information and work automatically, but this is supervised by a human being in a direct or indirect way. This person often receives the title of //operator//, which is the person who looks at the screen or otherwise receives the events, whether it might be by means of a smartphone device or similar, by e-mail or logs registered with another tool. The "how" does not matter, the important thing is the fact that someone is minding the system.
  
-{{  :wiki:notice_ways.png?300  }}+{{  :wiki:notice_ways.png  }}
  
 On the other hand, there are certain people called //system administrators//  in general or //infrastructure staff//, those who, when something happens, receive a call from the operator saying: "Hey, we have got a problem here," or a direct notification sent automatically by the system, warning them of an event, which is frequently sent by SMS or email. On the other hand, there are certain people called //system administrators//  in general or //infrastructure staff//, those who, when something happens, receive a call from the operator saying: "Hey, we have got a problem here," or a direct notification sent automatically by the system, warning them of an event, which is frequently sent by SMS or email.
Line 190: Line 185:
  
 Maybe, but from our experience, each client works in a certain way and regardless of how much we know about monitoring, we may not know more about how your infrastructure was configured than you do. Monitoring easy tasks presents no problems, the hard job is to adapt monitoring to your business without having to adapt your business to monitoring. Not an easy task. More than 800 pages await, if you wish to discover the best way to monitor your organization with Pandora FMS. It is a challenge, but one we believe is well worth the effort. Maybe, but from our experience, each client works in a certain way and regardless of how much we know about monitoring, we may not know more about how your infrastructure was configured than you do. Monitoring easy tasks presents no problems, the hard job is to adapt monitoring to your business without having to adapt your business to monitoring. Not an easy task. More than 800 pages await, if you wish to discover the best way to monitor your organization with Pandora FMS. It is a challenge, but one we believe is well worth the effort.
 +
 +[[:en:documentation:start|Go back to Pandora FMS documentation index]]
  
  
ºº