C100 / Export statistics wrong time-period / Howto change?

Unanswered Question
Aug 25th, 2008
User Badges:

If we have a look at the "Monitor, Internal Users" we can change the time range from "day" to "week" to "month".

If we want to export the same displayed time range as CSV for Excel, we don't get the same period... :oops:

Choosing the "day" for displaying in the browser (24 Aug 2008 16:00 to 25 Aug 2008 16:45 (GMT +0200) Data in time range: 100.0 % complete), we get the URL:
and the CSV-data looks like this:

Begin Timestamp,End Timestamp,Begin Date,End Date,Internal User,Clean Messages
1219586400.0,1219589999.0,2008-08-24 14:00 GMT,2008-08-24 14:59 GMT,[email protected],1
You can see, this is just an HOUR and not a DAY.

The same for the time-range "month":
Begin Timestamp,End Timestamp,Begin Date,End Date,Internal User,Clean Messages
1217023200.0,1217109599.0,2008-07-25 22:00 GMT,2008-07-26 21:59 GMT,[email protected],5
This is just a DAY not a month...

How can I export the same time-range to Excel as shown in the Browser with the same values for incoming/outgoing number of mails?
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Douglas Hardison Mon, 08/25/2008 - 19:44
User Badges:
  • Cisco Employee,

Hi Pat,

What version of AsyncOS do you happen to be running on your Ironport?
I've not seen this behavior before, and wonder if perhaps it's new.

Douglas Hardison Tue, 08/26/2008 - 14:46
User Badges:
  • Cisco Employee,


This appears to be an issue with the reporting export in the version you are using.

As with any defect, you can query your account team for the status of its progression.


Pat_ironport Tue, 08/26/2008 - 15:10
User Badges:

Thank you for the fast answer, whardison.
I will have a look in the next versions for a possible fix.

Do we have any possibility for a workaround?
(Manually change the URL or somehting else?)

Douglas Hardison Wed, 08/27/2008 - 13:14
User Badges:
  • Cisco Employee,


At this point in time, I do not know of a workaround. The issue is still currently being investigated.

Instead of using the export button on the reporting page, you might consider using an automated script as described in the AsyncOS Users Guide, under the section 'Retrieving CSV Data via Automated Processes'.

Pat_ironport Wed, 10/08/2008 - 08:31
User Badges:

We have installed the AsynchOS version 6.3.6-003 today.
Can it be that this error is fixed now?

If I repeat the export steps for the time ranges, the CSV seems to contain the matching amount of data for that range.

Any "official" answer for this?

Douglas Hardison Thu, 10/09/2008 - 13:18
User Badges:
  • Cisco Employee,

Hi Pat,

I dot not see an official statement that this particular issue was singled out for inclusion in a new release. That being said, any reporting issues resolved in this (or intermediate point versions not publically released ) could most definitely overlap the issue and allow the export to work properly.



This Discussion