Jacarta interSeptor Pro 24 ISPRO is available in 3 models, equipped with 8, 16 or 24 environmental ports.Each interSeptor Pro environmental port can monitor a. InterSeptor Pro provides an. The Jacarta interSeptor Pro security sensor is a magnetic reed switch that can be.
Jacarta product philosophy is to provide highly reliable solutions that are not only straightforward to install and use, but also extremely cost- effective, so that the return on investment for our end- user customers can be as rapid as possible. Monitoring: Power. Air- conditioning and air flow. Temperature. Humidity. Water leak detection. Smoke detection. Measuring and monitoring these, amongst other parameters in the datacentre is crucial to understanding the IT infrastructure impact on the corporate carbon footprint for the environment and operational costs.
Without monitoring and trending these key factors, the organisation cannot measure or audit how the datacentre is performing against costs. These costs are certain to escalate as power and cooling expenses continue to rise in the future. Jacarta interceptor and interceptor Pro models bring all the benefits of a single device which monitors your datacentre 2.
It can shows the following as measured by the Jacarta inter. Septor Pro device: Remarks. Add Sensor. The Add Sensor dialog appears when adding a new sensor on a device manually. It only shows the setting fields that are imperative for creating the sensor.
Therefore, you will not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later. Select the measuring points of inter. Septor Pro device you want to monitor. PRTG creates one sensor for each measuring point you choose in the Add Sensor dialog.
The settings you choose in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page: Sensor Settings. On the details page of a sensor, click on the Settings tab to change its settings. Note: Usually, a sensor connects to the IP Address or DNS Name of the parent device on which you created this sensor.
Ethernet Environmental Monitoring Unit Quick Installation Guide 5519.12001.00, Rev. 2.5a www.jacarta.co.uk T.
See the Device Settings for details. For some sensor types, you can define the monitoring target explicitly in the sensor settings. Please see below for details on available settings.
Sensor Name. Enter a meaningful name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets. Parent Tags. Shows Tags that this sensor inherits from its parent device, group, and probe. This setting is shown for your information only and cannot be changed here.
Tags. Enter one or more Tags, separated by space or comma. You can use tags to group sensors and use tag.
Tags are not case sensitive. We recommend that you use the default value.
You can add additional tags to it, if you like. Other tags are automatically inherited from objects further up in the device tree. These are visible above as Parent Tags. Priority. Select a priority for the sensor.
This setting determines where the sensor is placed in sensor lists. Top priority is at the top of a list. Choose from one star (low priority) to five stars (top priority). Primary Channel. Note: Overview.
Chart Type. Define how different channels will be shown for this sensor. Show channels independently (default): Show an own graph for each channel. Stack channels on top of each other: Stack channels on top of each other to create a multi- channel graph. This will generate an easy- to- read graph which visualizes the different components of your total traffic.
Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Settings settings). Stack Unit. This setting is only available if stacked graphs are selected above. Choose a unit from the list. All channels with this unit will be stacked on top of each other. By default, you cannot exclude single channels from stacking, if they use the selected unit. However, there is an advanced procedure to do so.
Inherited Settings. By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Rootgroup's settings. To change a setting only for this object, disable inheritance by clicking on the check mark before the corresponding setting name.
You will then see the options described below. Scanning Interval. Select a scanning interval (seconds, minutes, or hours) from the list. The scanning interval determines the time the sensor waits between two scans. You can change the available intervals in the system administration. When a Sensor Reports an Error. Define the number of scanning intervals that a sensor has time to report an error before the sensor will be set to a Downstatus.
The sensor can try to reach a device several times, depending on the setup you can specify here, to help avoid false alarms if the monitored device has only temporary issues. For previous scanning intervals with failed requests, the sensor will show a Warning status. Choose between: Set sensor to . If the following request also fails, the sensor will show an error. Set sensor to . It is not possible to set a WMI sensor . The corresponding settings from the parent objects will always be active.
However, you can define additional settings here. They will be active at the same time as the parent objects' settings. Schedule. Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week.
With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings. Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active at the same time. Maintenance Window.
Not set (monitor continuously): No maintenance window will be set and monitoring will always be active. Set up a one- time maintenance window: Pause monitoring within a maintenance window.
You can define a time span for a monitoring pause below and change it even for a currently running maintenance window. Note: To terminate a current maintenance window before the defined end date, you can change the time in Maintenance End At field to a date in the past. Maintenance Begins At. This field is only visible if you enabled the maintenance window above. Use the date time picker to enter the start date and time of the maintenance window. Maintenance End At.
This field is only visible if you enabled the maintenance window above. Use the date time picker to enter the end date and time of the maintenance window. Dependency Type. Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another.
You can choose between: Use parent: Pause the current sensor if the device, where it is created on, is in a Down status, or if the sensor is paused by another dependency. Select object: Pause the current sensor if the device, where it is created on, is in an Down status, or if the sensor is paused by another dependency. Additionally, pause the current sensor if a specific other object in the device tree is in a Down status, or if it is paused by another dependency.
Select below. Master object for parent: Make this sensor the master object for its parent device. The sensor will influence the behavior of the device, where it is created on: If the sensor is in a Down status, the device will be paused.
For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused.
You can check all dependencies in your PRTG installation by selecting Devices . Click on the reading- glasses and use the object selector to choose an object on which the current sensor will depend. Delay (Seconds)Define a time span. After the master object for this dependency comes back to an Up status, the beginning of the monitoring of the depending objects will be additionally delayed by the time span you define here. This can help to avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Master object for parent.
In this case, please define delays in the parent Device Settings or in the superior Group Settings. User Group Access. Define which user group(s) will have access to the object you're editing.
A table with user groups and types of access rights is shown: It contains all user groups from your setup. For each user group you can choose from the following access rights: Inherited: Use the access rights settings of the parent object. None: Users in this group cannot see or edit the object. The object neither shows up in lists nor in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible. Read: Users in this group can see the object and review its monitoring results.
Write: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings. Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings.
You can create new user groups in the System Administration. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option. For more details on access rights, please see the section User Access Rights. Channel Unit Types. Bandwidth. Memory. Disk. File. Custom.
Note: More. Knowledge Base: My SNMP sensors don't work. What can I do? Edit Sensor Channels. To change display settings, spike filter, and limits, switch to the sensor's Overview tab and click the gear icon of a specific channel. For detailed information, please see the Sensor Channels Settingssection. Notifications. Click the Notifications tab to change notification triggers. For detailed information, please see the Sensor Notifications Settingssection.
Others. For more general information about settings, please see the Object Settingssection. Sensor Settings Overview. For information about sensor settings, please see the following sections.