EdgeSight: How to Change Reporting Schedules


EdgeSight allows you to schedule any of its reports for automatic running and delivery to either a file share or e-mail address(es).  Did you know that you can modify when these reports are run?  I will show you in this post where to find the reporting schedules and how to modify when they run.

EdgeSight Console: Configure Tab

Open your EdgeSight Console and click on the Configure Tab


On the left-hand-side, under Server Configuration, click Reporting Services and then Schedules


You will now see the built-in schedules and when they run in EdgeSight


Simply click on the Edit button and change the schedule to suit your purposes.  You can also create your own schedules here depending on your needs.



As always, I welcome all comments and questions especially about EdgeSight.


7 thoughts on “EdgeSight: How to Change Reporting Schedules”

  1. Hi, Alain,
    I’ve set up a schedule to run on the first of every month. I am now setting up a subscription to a report (Session Count for a particular department). How do I set the date range for the report to coincide with each new month. For instance, I want the report run on June 1 to cover May 1 to May 31. The report on July 1 to cover June 1 to June 30, etc.



    1. Spencer,

      Once you set the date range for the scheduled report, reporting services should automatically run it for the next date range as long as the report schedule is monthly.

      Let me know how it goes.

      Thanks for reading,

      1. Thanks for the response. Unfortunately, I have left that project and will not be able to see how it went. I’ll trust what you say and assume it does for the next time I run into it! 🙂

  2. I seem to be having an issue with the subscriptions. I had to create it twice because the the first never showed up in my subscription tab, but I am still receiving the emails for it. Is there any other place I can change or delete a subscription?


  3. I’ve setup a subscription with scheduling as demonstrated here. However, I noticed that the data seems to be skewed in some of the reports. For example, it shows the average CPU utilization to be way lower (5%) than i actually know it should be. I have a feeling this is because it is an average across a 24 hr period (the servers are only used heavily 12 hrs a day, light load probably 2 additional hours). Is there a way to modify the time period from which this data is collected? Say 7 am to 7 pm as opposed to 24 hrs. I know the real time reports give this option, but I was unable to subscribe to a real time report.

    1. Bowen,

      You are correct that the average reports are for a 24 hour period. I only see 3 ways to get around this.
      1. [Good] You change your XenApp workers to upload to the database at either end of your peak times (for example 6AM and 8PM) and then kick off your reports shortly afterwards. Again, this will still give you a day’s average, but will be more timely for your environments. You may still have to get the data as a CSV and massage it in a spreadsheet program.
      2. [Better] Change your subscribed reports to run every day and sort them by hour. You should then see the CPU utilization each hour of the previous day. Again, you may have to manipulate the information in a spreadsheet to get what you are looking for.
      3. [Best] You disable (via script/scheduled task) your EdgeSight agents during your off hours. Then the only data collected is when your serves are heavily used.

      I will cover this problem more in-depth and use a custom SQL query to get the information you’re looking for in a future post.

      Thank you for reading,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.