SolarWinds

In case your organization is using OPTIC DL to manage and analyze different types of data, and also SolarWinds to optimize and troubleshoot your infrastructure, you might need to integrate both tools and get a birds-eye view on your metrics and information. Here is an example how ZigiOps can do that for you.

The integration platform collects metrics from SolarWinds (like host, cluster, VM metrics, ESXi host, etc.) and reports them to OPTIC DL. ZigiOps gives you granular control over data filtering to make sure it collects only the required SolarWinds data. You also have access to the data sets, which define what types of metrics are reported to OPTIC DL. For example, we provide two collections which are hosts and ESXi hosts metrics.

Additionally, ZigiOps detects changes to the metrics in SolarWinds, sends them to OPTIC DL and updates the existing data.

You can sync events/alerts from SolarWinds with cases in Salesforce automatically with ZigiOps. If your main APM system is SolarWinds and you’re using Salesforce in parallel, our integration will help you connect the two apps.

When an event/alert is created in SolarWinds, the integration will detect and collect it and create a related case in Salesforce. You have a high degree of control of the data filtering functionalities of the platform to make sure it collects only the necessary SolarWinds events/alerts. Besides that, you also have full control of the data field mapping settings that define how ZigiOps reports data to Salesforce. Regular fields, custom properties and lifecycle fields are all in sync.

Updates in SolarWinds for events/alerts already transferred to Salesforce are collected and transferred to the related case in Salesforce for regular fields, custom fields and lifecycle fields.

If your main APM system is SolarWinds and you want to log SolarWinds events/alerts as issues in Jira Service Management automatically, you can use ZigiOps’ integration to do this.

When an event/alert is triggered in SolarWinds, ZigiOps will detect it automatically and log an issue in Jira. You have control over the data filtering settings to make sure the integration collects only the necessary SolarWinds events/alerts. You also have full control over the data field mapping settings to define how ZigiOps reports data to Jira SM. Regular fields, custom properties and lifecycle fields are part of the integration.

ZigiOps automatically collects updates in SolarWinds for events/alerts already transferred to Jira SM . It then synchronizes them with the related issue in Jira SM for regular fields, custom fields, lifecycle fields and comments.

If your main monitoring system is SolarWinds and you want to sync events/alerts from it into incidents in ServiceNow, this integration will do that for you.

When an event/alert is created in SolarWinds, ZigiOps will pick it up automatically and log an incident/change in ServiceNow. You have control of all data filtering functionalities to make sure the platform collects only the SolarWinds events/alerts that you need, and to filter out the noise. Additionally, you have full control of the data field mapping settings that define how ZigiOps reports data to ServiceNow. Regular fields, custom properties and lifecycle fields are part of the synchronization.

Updates in SolarWinds for events/alerts already transferred to ServiceNow are collected and synchronized with the related Incident/Change in ServiceNow for regular fields, custom fields, lifecycle fields and comments.

You can use this integration if your main APM system is SolarWinds and you want to synchronize events/alerts, topology and metrics between SolarWinds and Micro Focus Operations Bridge.

When an event/alert is triggered in SolarWinds, the integration will detect it automatically and create an event in OpsBridge. Our platform gives you granular control over data filtering to make sure it collects only the required SolarWinds events/alerts. You also have control over data field mapping to define how ZigiOps reports data to OBM. Regular fields, custom properties and lifecycle fields sync automatically.

Updates in SolarWinds for events/alerts that have already been transferred to OpsBridge are detected and gathered at a scheduled interval (e.g. every minute). After that, ZigiOps syncs them with the related events in OpsBridge based on the OBM event correlation logic (correlation key, close key).

ZigiOps collects topology (nodes, interfaces, or other types) from SolarWinds and reports it to OBM. It also detects changes to the topology in SolarWinds, sends them to OBM and updates the existing topology.

ZigiOps collects metrics from SolarWinds and reports them to Micro Focus Operations Connector OA DB; they are then accessible in OBM Performance Perspective.

This integration allows collecting events from SolarWinds to create events in Splunk. To collect events from SolarWinds, ZigiOps sends HTTP requests at a scheduled interval and then forwards them to Splunk. With ZigiOps’ SolarWinds Splunk integration, you can connect SolarWinds to either Splunk Enterprise or Splunk ITSI: we’re supporting both tools.

The platform then syncs all related details and information, keeping Events in both software tools aligned. When a user closes a SolarWinds Event, the corresponding Event in Splunk Enterprise or Splunk ITSI is automatically closed by the data integration platform.

Thanks to our flexible data mapping functionalities, you can sync all related fields like Affected Entity, Description, Host, Index, Severity, Source, Source Type, and more.