Jump to content

Search the Community

Showing results for tags 'shared alerts'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Features Discussion
    • Getting started
    • Release Notes
    • General
    • Industry Chats
    • Feedback & Feature Requests
    • Agent
    • User Portal and Web App
    • Domotz Mobile App
    • Domotz Hardware
    • Public API for Developers
  • Third Party Hardware
    • Power Distribution Units (PDU) & Smart Power Plugs
    • Managed Network Switches
    • Device Configuration Management - Backup & Restore
    • Gateway/Controller Integrations
    • Wi-Fi Access Point and Controllers Integrations
    • Audio Video and Multimedia Integrations
    • Other Devices
    • Manufacturer Support
    • Domotz Agents on 3rd party platforms

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. Giancarlo

    02/18 - 2020 Release Notes

    This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App.  Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released.  February 18th, 2020  In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of  Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 2.9.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.8.5 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.7 Domotz Pro WebApp, Desktop App and Portal are already updated to the latest version What's new: Autotask PSA integration: it is now possible to connect a Datto/Autotask PSA portal into Domotz. Autotask PSA will become one of the available Contact Channels available to be used in Shared Alerts. This means that Domotz creates and update Autotask PSA tickets when a specific event occurs on the networks or devices monitored through Domotz. Domotz creates an Autotask PSA service ticket for any specified alert within Domotz. The same ticket is updated by Domotz automatically, in the case other events occur on the same network or device and as far as the ticket is still open in Autotask PSA. When the previous ticket is closed and a new event occurs on the same network or device, a new ticket will be opened and a reference to the previous ticket is provided. Users are also allowed to associate each Agent to one specific Account so that every time the ticket is automatically created in Autotask PSA, it flows under that specific Account. Cisco Meraki Access Points: with Wi-Fi Access Point advanced monitoring, it is now possible to monitor Cisco Meraki Wi-Fi Access Points and their connected clients: Monitor signal strength of AP by channel Monitor signal strength of connected clients Monitor access point traffic utilization Monitor Wi-Fi clients traffic utilization Retrieve additional info about connected Wi-Fi clients (e.g. Operating System, Description, connected Channel and SSID, etc) Company Structure Reports: under the Company Structure Portal it is now possible to download CSV or XLS reports about: All agents and customer details configured under different teams of the structure Statistics on the Event generated by Important Devices or Networks Details on Customer Chats through the Customer Facing App For more information about the Company Structure, contact sales@domotz.com Improvements: Higher number of organizations supported within ticketing systes: the maximum number of Organizations and Accounts in Zendesk and Autotask PSA for the association with Domotz has been extended to 1500 Cisco Meraki Switch: it is now possible to retrieve the bandwidth usage associated to each port of the Cisco Meraki switches and control the power status of each PoE port. Moreover for each device it is also reported the Firmware Version and the Serial Number Cisco Meraki Switch - Additional data: for each port of the Cisco Meraki switch is is now possible to retrieve additional information such as: Isolation Enabled VLAN Allowed VLANs RSTP status STP Guard status Type Link Negotiation Total traffic Direct Link to Domotz WebApp in notifications: when you receive a notification (either through email, Ticketing System, Slack or any other contact channel) you will now be provided with with a link to access directly the device or the network (Domotz Agent or Site) which has generated that Alert New Field in Customer Management: it is now possible to specify a Contract ID within the Customer Management data. This information is also reported under the list of Subscriptions in the Portal (together with the Customer ID). Shared Alerts on Multi-select: it is now possible to aply Shared Alerts to multiple devices with one click using the multi-select functionality Fix: Zendesk integration has been fixed in the association between Agents and Organizations Push notifications on Android appeared with blank icon Excel Import functionality on Domotz Desktop App has been fixed Generating a monthly PDF report on an Agent without Customer Management information completely configured (missing street) resulted in error Domotz Desktop App prevented the usage of the Cmd+P/Ctrl+P for printing system wide Issue when opening multiple TCP Tunnels Domotz Eyes did not display numeric values for SNMP OiD monitoring, when value was 0 Device Notes with carriage returns were not properly managed Known limitations: VPN on Demand is currently not supported on Luxul Router based Agents. Expected resolution within Q1 2020, or as soon as Luxul team will provide Domotz with the API resources to make this available. VPN on Demand on NAS based Agents is only available with an offline request: new packages are available on external links, but not yet available on the NAS stores. Expected resolution before end of March 2020. Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device. This affect also some type of switches which appear as multiple instances on Domotz when VLANs are configured Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Static IP address on the Domotz Box cannot be configured before configuring the Agent
  2. Giancarlo

    12/18 - 2019 Release Notes

    This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App.  Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released.  December 18th, 2019  In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of  Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 2.7.2 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.8.3 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.7 Domotz Pro WebApp, Desktop App and Portal are already updated to the latest version What's new: Zendesk Integration: it is now possible to connect a Zendesk Account into Domotz. Zendesk will become one of the available Contact Channels available to be used in Shared Alerts. This means that Domotz creates and updates Zendesk tickets when a specific event occurs on the network or devices monitored through Domotz. Domotz creates a Zendesk service ticket for any specified alert within Domotz. The same ticket is updated by Domotz, in the case other events happen on the same network or device and as far as the ticket is still open in Zendesk. Users can also associate each Agent to one specific Organization so that every time the ticket is automatically created in Zendesk, it flows under that specific Organization. Improvements: Much faster Global Dashboard and flow: Domotz has introduced optimizations in the loading of multiple network data within the Global Dashboard and in the navigation across multiple Agents with hundreds of devices. The following are the recorded stats performed on accounts with hundreds of networks to be monitored and thousands of devices in each network: Before Optimization: Global Overview loaded in 22 seconds Overview data: 12MB - 855Kb compressed Complete load of a single Agent with ~1000 devices in 18 seconds After Optimization: Global Overview loaded in 10 seconds Overview data: 1.4MB - 39.4Kb compressed Complete load of a single Agent with ~1000 devices in 6 seconds Agent Activity Logging: all the activities performed on the administration of Agents (new Configuration, Change of names, Delete, etc) are now tracked with the specific user performing the action within the History list (Portal -> Subscriptions) Shared Alert Configuration directly available in the WebApp: Domotz users can now configure the Shared Alert profiles directly from within the App and WebApp so that it is easier to change configurations and review the policies available for the Shared Alerts (including all the different and possible contact channels available). Fix: Activity logs on the Report and Logging section disappeared Cisco Meraki switch integration reported invalid int conversion for the mapping of devices on the interfaces WebApp did not work on Edge browser Mobile App did not work on iOS version older than 11 Known limitations: Within the Zendesk integration, the association between Agents and Organization is partially working. Expected resolution before end of December 2019. VPN on Demand is currently not supported on Luxul Router based Agents. Expected resolution within Q1 2020, or as soon as Luxul team will provide Domotz with the API resources to make this available. VPN on Demand on NAS based Agents is only available with an offline request: new packages are available on external links, but not yet available on the NAS stores. Expected resolution before end of January 2020. Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device. This affect also some type of switches which appear as multiple instances on Domotz when VLANs are configured Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Static IP address on the Domotz Box cannot be configured before configuring the Agent
  3. Giancarlo

    03/13 - 2019 Release Notes

    This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. March 13rd, 2019  In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of  Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.12.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.4.4 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.7 Domotz Pro WebApp and Portal are already updated to the latest version What's new: Shared Alerts and webhook: with Shared Alerts, Domotz users can now define events for which the entire team would like to receive notifications either through emails or webhooks. Users can define alert profiles which can be applied either to devices or agents indifferently by any member of the team so that they are shared across the whole team. For example, this functionality can be used if the user is planning to feed alerts into a ticketing system or if he wants to send email alerts to an email address which is not configured as an account within Domotz Pro. This capability is available on Agents configured with the Premium Plan. Define a shared alert profile: It is now possible to create an Alert Profile using the available device or agent events already available within Domotz Pro (Agent disconnection, Device Online/Offline, Device Heartbeat, etc). Within the profile, users can also define the recipients which should be notified for those events either in the form of email addresses or webhooks. The Alert Profiles created will be shared across the whole team and can be modified in the case something changes in the team or infrastructure. Receive event notifications either through email or webhook: when the defined event occurs, users can be notified either through one or more email addresses (even if those email address are not connected to a Domotz Pro account) or by defining a URL where you want to receive an HTTP callback (webhooks). Associate the Alert Profile to specific devices or Agent: Once the shared alert profile has been defined, users can assign that profile to specific devices or Agents. If, for any reason, the user need to change destination email address or URL for the HTTP callback (webhooks), he can just change the alert profile configuration once, and that will be applied to all the devices and Agents associated with that shared alert profile. Every single member of the team will have access to the alert profiles, to make the Alert configuration easier and shared across the whole team. Slack Integration: following this guide it is possible to create Slack Endpoint which can be used into the Alert Profile configuration as contact channel. Domotz users can now receive alerts directly on their Slack channels, with color coding which match the criticality of the alert. Improvements: Device Response Time: this feature is now available to 99% of the Domotz Agent packages available for all the architectures (including Synology and QNAP NAS, Raspberry with SNAP package, Windows Agent, etc). Premium plan is required. PDU support: SnapAV Wattbox newer firmware/models support Fix: Public API: Datetime in filter parameters don't accept timezone. Documentation fixed. Public API: missing X-API-Key in access control. Due to the issue the usage of Public API was limited on some programming languages. CyberSecurity feature: a wrong icon was shown when UPnP scan was paused. PDU configuration: device filtering within PDU Config selection not working CyberSecurity feature: a false 'All alerts are disabled for this Agent' on security section Cisco SG250/350 PoE capability using a wrong MIB value generated the side-effect of not having PoE on Domotz Ruckus Unleashed controller Not able to login Ruckus Unleashed FAT AP containing more than one AP-s in its API response Known limitations: Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Static IP address on the Domotz Box cannot be configured before configuring the Agent Multiple Devices logically connected to a Managed Switch Port: in case of WiFi AP connected to a switch port, the information is not available at the WiFi AP info __________________________________________________ Few screenshots related to the new functionalities: Define a shared alert profile: Configured Shared Alert profiles in the Portal: Define a new Shared Alert profile: Associate the Alert profile to specific devices or Agent: Associate the profile to a specific device: Change profile for the specific device: Associate the profile to a specific agent: Create an Slack Incoming WebHook and use in Domotz: Create a Slack incoming WebHook and use it in the Shared Alert Profile as an additional channel: Start receiving alerts directly on your Slack Channel, shared among your team:
×
×
  • Create New...