Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

For on-prem sites, customers may wish to parallel processing using multiple proxies. For example, my organization has six major data centers. In each data center, I have dozens of servers. I would like to scan all of my server eventlogs on a frequent basis for errors and warnings. By deploying a proxy to each location, I can parallel process. This results in a new challenge: I want this to be a single script so that the data is merged together into a single view, but I somehow need to tell each proxy which servers it's responsible for. This article describes an approach to solve this problem.

Instructions

This is just one example but could be modified for many needs

  1. Create a script that collects all servers from Active Directory and shows the OU for the server. Each of the data centers will likely be organized into OU's.
    This is establishing the input for the proxies
  2. install a proxy in each data center and create a corresponding ConnectID
  3. In each ConnectID, create a variable called OU, paste a list of OU's this proxy will be responsible for with comma separation
  4. Create a script to query the evenlogs
    1. Use the data query feature to query the data from your AD script, retrieving a list of servers
      1. Ideally restrict the query to only the servers in the target OU
    2. Loop through the list of servers collecting data from each
      1. Consider using PowerShell parallel processing
  5. Data should be returned and merged automatically by Cloudbridge


Filter by label

There are no items with the selected labels at this time.



  • No labels