on 2018 Oct 17 3:40 PM
Hi All, we are now on 4.2 SP04 and see a possible new probe you could help us with:
- We need a probe that restart only the Web Intelligence processing servers under certain conditions
- We already get an email alert via monitoring IF there are 20+ concurrent reports running AND they are doing so over 30 minutes
- We now manually fix this by restarting the Web Intelligence servers manually
- We would like to use the "Diagnostics Probe" to achieve this with a modified where clause
Can anyone help us with this "where" definition?
The original is:
Where SI_PROGID='CrystalEnterprise.Server' AND SI_SERVER_KIND NOT IN ('aps') AND SI_NAME NOT LIKE '%AdaptiveProcessingServer%' AND SI_NAME NOT LIKE '%AdaptiveJobServer%'
We have 2 nodes and 4 Web Intelligence processing servers.
Would this work ?:
Where SI_SERVER_KIND IN ('aps') AND SI_NAME LIKE '%WebIntelligenceProcessingServer%' AND SI_NAME LIKE '%AdaptiveJobServer%'
What do you think?
Thanks
Request clarification before answering.
This environment needs to be properly sized with adequate resources allocated and then load tested for performance so it doesn't collapse under the weight of ~50 jobs that are running for ~15 minutes apiece.
Also Denis is right as usual most likely: the reports are probably very inefficient to begin with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
73 | |
21 | |
9 | |
8 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.