Active ticket system monitoring

Next topic

Author	Message
Nathan Kelly	Wednesday 09 April 2008 6:43:23 pm Hi All, I'm setting up to develop a new site with eZ and the first main project to tackle is to implement a ticket system, for this I plan to use the Ticket System contribution and modify it to suit certain requirements. One of the requirements my client has asked for is an active monitoring interface, basically what they want to be able to do is keep the monitoring page open on a dedicated machine that updates automatically when ever a ticket is issued. I want to avoid the "page refresh every ## seconds" approach because this I suspect will use up a lot of bandwidth, the ideal solution would be one that doesn't need to refresh an entire page but rather only updates 1 element on the page when a ticket is issued. I was thinking that this might be possible to achieve with a combination of cronjobs, the built in workflow system and ajax? But unfortunately I don't have much experience with any of these operations. I wonder if anyone here can help me with some ideas of where to start with something like this? Then again I might be looking at this all wrong and there may be a better way to achieve the functionality I'm after? Any ideas or suggestions would be appreciated. Cheers. Pardon me while I burst into flames...
Maxime Thomas	Wednesday 09 April 2008 11:49:26 pm Hi, I guess the best solution is to create an ajax timer that will check if a new ticket is available. You can post on a module with a specified function, something very light. Max Maxime Thomas [email protected] \| www.wascou.org \| http://twitter.com/wascou Company Blog : http://www.wascou.org/eng/Company/Blog Technical Blog : http://share.ez.no/blogs/maxime-thomas
Ekkehard Dörre	Thursday 10 April 2008 2:14:52 am Hi Nathan, ... or you implement a message queue system like Dropr: https://www.dropr.org/ You make a message, when there is a new issue (e.g. with http://serwatka.net/blog/ez_publish_3_8_new_custom_edit_handler ) and the other server gets it. Greetings, ekke http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing
Nathan Kelly	Thursday 10 April 2008 4:09:57 am Cool thanks for the replies so far guys. I should just make it clear that when I said they want a dedicated machine to monitor the system I meant basically just a pc with the browser open on the ticket page. Its not a cross server setup or anything like that. I think I might look into Maxime's idea of an ajax request set on a timer that just checks if a record has been added or updated. I'm still open to ideas though, this is a system that will need to handle a large amout of support tickets and will be constantly growing so I really need a robust solution. Cheers. Pardon me while I burst into flames...

eZ debug

Timing:	Jan 17 2025 17:26:34
Script start
Timing:	Jan 17 2025 17:26:34
Module start 'layout'
Timing:	Jan 17 2025 17:26:34
Module start 'content'
Timing:	Jan 17 2025 17:26:35
Module end 'content'
Timing:	Jan 17 2025 17:26:35
Script end

Main resources:

Total runtime	1.0740 sec
Peak memory usage	4,096.0000 KB
Database Queries	62

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	598.2656	152.1172
Module start 'layout'	0.0048	0.0025	750.3828	39.4688
Module start 'content'	0.0073	1.0651	789.8516	641.5703
Module end 'content'	1.0724	0.0016	1,431.4219	16.2422
Script end	1.0740		1,447.6641

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.2787	16	0.0002
Check MTime	0.0011	0.1053	16	0.0001
Mysql Total
Database connection	0.0007	0.0679	1	0.0007
Mysqli_queries	1.0171	94.7007	62	0.0164
Looping result	0.0005	0.0479	60	0.0000
Template Total	1.0460	97.4	2	0.5230
Template load	0.0019	0.1791	2	0.0010
Template processing	1.0441	97.2088	2	0.5220
Template load and register function	0.0001	0.0119	1	0.0001
states
state_id_array	0.0006	0.0601	1	0.0006
state_identifier_array	0.0022	0.2056	2	0.0011
Override
Cache load	0.0016	0.1480	31	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0431	3	0.0002
Fetch class attribute name	0.0010	0.0970	7	0.0001
XML
Image XML parsing	0.0016	0.1466	3	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0010	8	0.0000
General
dbfile	0.0020	0.1908	28	0.0001
String conversion	0.0000	0.0005	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
4	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 18 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs