Idea Details

WCC collector efficiency and speed required , PLEASE

Last activity 03-11-2019 11:20 AM
Steve Carrobis's profile image
03-24-2017 07:19 AM

The collector used to be so much faster, now that we are down to 2 tomcat's and the collector is "internalized" it appears to be very erratic in nature. 

If a job is created or removed it takes anywhere from 1-10 minutes, depending on when it was added. Like all tuning we should be able to change the polling... also it should NOT take 10 minutes to pull in new jobs when other products never had this issue. Neither did WCC for that matter, NOT that I remember anyway even when it was 11.0 

Maybe I am just getting old .. :-)

I will say WCC has come a long way and it was decent in 11.0 believe it or NOT, then 3 steps back in 11.3 but now the 11.4 is much better, i will grant that.. BUT efficiency and expedience of a batch GUI on events is ESSENTIAL. 1-10 minutes can make or break an Operations process. seeing the wrong state or the job not there, etc., is unacceptable. 

So please may we have the next release focus on what is truly important, speed of process...

 

Thank you 

 

Steve C.


Comments

04-04-2018 12:11 PM

THANK YOU Dan! 

04-04-2018 12:06 PM

The challenges currently faced with WCC 11.4 with timely status updates will be addressed in the 12.0 release. We generally talk about usability enhancements in terms of organization and navigation. Also included in this bucket is performance. We are planning to address the jobs status latency problem some customers experience also. I'm expecting very near real-time status accuracy with the upcoming release. I'm not sure how demonstrable the performance changes will be in upcoming sprint reviews. We will definitely communicate them whether they can be demonstrated effectively or not. Please attend the sprint reviews to watch and influence the product evolve.

 

Thanks,

 

Dan

04-04-2018 11:53 AM

Yeah I think the Reporting feature is what most of my clients dislike just because "who is going to come in to generate the report everyday and why cant they save my templates" complaint.

 

I would definitely want to be able to schedule and email reports rather than coming into WCC everyday and going through a bunch of manual clicks and then find out you picked the wrong values (!doh!)

04-04-2018 11:52 AM

also please give us a mechanism to force a collection. :-)

04-04-2018 11:46 AM

yes the collector was a perl program call to a java process in R11.0 before they internalized R11.3+ 

believe me i asked for that and also to be able to email reports like BOXI could do. schedule report run internally then send out report. 

then they dumped BOXI for Jasmin or whatever it is now. :-)

it's a process i know ..

04-04-2018 11:43 AM

Wasn't there a way to force the collector to run manually from the command line in the older releases? (11.0 and even 11.3 I think) and it got taken away with 11.3.5 + 

 

I found that to be a useful last resort option to get the flows and things back in sync, *cough* most of the times *cough*. I don't recall if there's an option to do this with the new versions anymore. Also the logging on the collector is not very useful even though you play around with the settings in the log4j files. A lot more logging, when needed, would definitely be useful. 

04-04-2018 11:38 AM

hey CA / Jean Paul. I had this out there for awhile and this is exactly the issue Lizzzie/Lisa and the rest of us face. 

03-24-2017 08:00 AM

Yes, we get many complaints from schedulers and operators that their jobs don't appear to be updated when it turns out to  be a very slow collector.