@bibarrav

Hi,

Probably it is a WebLogic issue. If it is a “Devlopment Mode” WebLogic domain; you should not see the “Change Center” in WebLogic console. But, in your sceen capture “WebLogic Change Center” is available (attached below). We are recommending to setup your WebLogic domain from scratch as Development mode domain.

Regards…

image.png

Thanks,

The point 1 resolved it. OHS was being used here. Using the listen port helped to resolve the issue.

Regards,

Thanks a lot !

It is working fine now after removing the boot.properties file.

Regards,

Hi,

We have another product named WL-OPC for systems that have many domains and these requests can be made in there.Otherwise, you can define many rules as you want in WL-OPC.

Even there is no need for email, when you using WL-OPC console, you can monitor every notification from all domains in one operation center. More information http://www.wlsdm.com/wl-opc/index

Regards.

Hi,

Are you sure you have created HTTP transactions for the relevant managed server? Remember you need to create real traffic to exceed 8kb buffer size for the response times monitoring. So, at least there must be +100 request after managed server restart.

Are you sure you have selected the right managed server on the “Response Times” page? (Please take below screen capture as a reference)

2..jpg

Go to “Configuration > Monitoring & Diagnostics > Response Times (tab)” page and check the status. Is there any server needs to be restarted?
3..jpg

Kind Regards…

Please try registering the domain by using the “overwrite” and retry delete domain.

ow.jpg

Hi,

It looks like a WLSDM DB issue.

This is might be happening because you do not have enough disk space on the machine.

Please check your disk for enough space.

After that please restart the (only) AdminServer.

Kind regards.

Hi,

Unfortunately, we are not supporting “bash 3.2” version. At least you have to use “bash 4.x version”. Adding compatible bash version as below.

Here are our recommendations:

Our recommended OS is Linux. (centOS, Red Hat… etc.). You had better choose Linux servers. This information is already available in the help at the “prerequisite” section.

Upgrade your bash version to 4.1 at your current working Solaris server.

Kind Regards…

Hi,

This is a cache issue.

As a workaround: Please restart your WebLogic AdminServer to apply your new license.

Hi,

This is an “Internet Explorer” issue (also, previous issue too).

Please prefer the Chrome or the Firefox as browser while we fix the problem in next WL-OPC release.

Kind Regards…

Hi,

This script is endless; you should echo a result for capturing a variable in WLSDM.

You should use the ping command like i.e. “ping $servername –c 1” then extract output from the ping command.

We are recommending you to use the script which is available in WLSDM README for pinging database. Please follow the readme link here: http://www.wlsdm.com/docs/README#VI.ConsoleUsage&DevOpsMBean

Also we are pasting below.

Step-1 Write Shell Script: Ping database and calculate database response time using WebLogic API (weblogic.jar)

#Variables _dbStatus=0 #0:DB_DOWN,1:DB_UP #start DB Ping _startTime=$(($(date +%s%N)/1000000)) _pingResult=`java -cp weblogic.jar utils.dbping ORACLE_THIN $YOUR_USER_NAME $YOUR_PASSWORD $YOUR_IP:$YOUR_PORT/$YOUR_SERVICE_NAME` _endTime=$(($(date +%s%N)/1000000)) _dbResponseTime=`expr $_endTime - $_startTime` if [[ "$_pingResult" == *"Success!!!"* ]]; then _dbStatus=1 #echo "Database connection SUCCESS!!!" #DB_UP echo DatabaseStatus=$_dbStatus else _dbStatus=0 #echo "Database connection FAILURE!!!" #DB_DOWN echo DatabaseStatus=$_dbStatus fi echo DatabaseResponseTime=$_dbResponseTime```

Hi Jeba,

First of all your WLSDM version is not the latest; please upgrade to v3.4.1 (it will took about 5 min). Please do a fresh installation. This domain was open for all the metrics about “STORE DATA” feature. That’s why you faced this issue.

Let us analyze more. Is this thread is in ManagedServer or AdminServer? We need below information to help you.

Could please at least take 3 thread dump for AdminServer and ManagedServer then send us to us? (thread dump: kill -3, or from WLSDM console) Could you please zip all WLSDM log files and send to us? (Available at WLSDM\logs folder) Could you please runt this command and share the output with us? cd $DOMAIN_HOME{WLSDM_RUNTIME_FOLDER}
du -sh * Could you please share the WLSDM version?

We are suspecting about data archive. As a workaround please DISABLE all your (make OFF) data archive settings. Go to “System Settings > system.archive (tab)” page and OFF all archive settings if they are currently ON. Then restart only AdminServer then observe the new states about high CPU consumption.

Kind Regards…

@whching said:

Hi @wlsdmsupport

I am just start looking at WLSDM, what is the difference of having one agent per cluster against one agent per managed server?

BTW, where I could find the resource overhead when WLSDM is used on managed servers? say, how much more heap memory it will use and how about any extra I/O it would introduced?
Thanks

Regards,
Rock

Hi,

If you have two member cluster and these members are on different machine then install two agent. If you have 4(four) member cluster and these members on two machine (two managed server per machine). Then install two agent (same with previous). Much agent, much traffic. Same behavior, same machine… Then go for one agent.

More information is available on README: http://www.wlsdm.com/docs/README#IV.Installation

WLSDM runs on AdminServer and you should not install any application on WebLogic admin console. So, it’s run-time console, should not affect your domain. WLSDM’s AdminServer overhead is negligible; one of the least overhead in the market; because we are not injecting any code to run-time classes. Maximum overhead for the managed server (considering backend monitoring is open) is about 3%-4%.

You had better, test on your current domain; because your domain is extra ordinary and you will see that WLSDM would be one of the best solution for this domain and its infrastructure.

Regards…

@jeba

Hi Jeba,

Also, check “store data” for back-end monitorings. It may generate too large data sets. especially if the “WebLogic Diagnostic Volume” set high for the related managed server.

Capture4.PNG

I enabled the store option for all of our datasources. So, in total there were around 75. Would this be an issue?

75 data sources cost you avg ~30 Mb per day (it depends on your metric instance count). If you have enough disk space it is not an issue.

How can I control the retention period for these metrics collections?

You can change the archive date range from the “Configuration> WLSDM System Settings” page. Archive module purges your data beyond the given date range. But do not reduce the date range instantly. You have too much data on your database and it may cause too much memory consumption. Prefer gradual reduction (like 3 or 5 days).

“system.archive.metric.data.range”

Capture2.PNG

Regards.

@jeba

Hi Jeba,

WLSDM does not have the feature for your requirement which is giving a threshold for the specific IP/hostname.

But it could be a nice feature, we will evaluate this feature for the next releases.

Regards.

Hi Tom,

You can filter back-end dashboard threshold value in “Configuration > WLSDM System Settings > system.monitoring > system.monitoring.diagnostic.backend.event.filter.threshold” property. Click edit button and give threshold value as 1000 (ms).

Regards.

1.png

@ozhana

Hi,

Are you sure all access and diagnostic logs are backuped?

Which WLSDM version are you using?

Kindly, please send reply at [email protected] email address.

Regards.

Hi Vivek;
Actually 11g and 12c offers same health dashboard. Something is wrong about your 12c WebLogic environment.
Could you please zip $domain_home/WLSDM/logs folder and attach screen capture to support (at) wlsdm.com email.
Regards…

Hi,

Today we have worked on SOA-11g environment. JVM Resources Page and GarbageCollection Page problem has been resolved.

Please do the following when you face such a problem in another domain.

Kind Regards…

Backup startWeblogic.sh file of the domain

Add the “-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder” parameter to JAVA_OPTIONS in the file

JXM.Values.JVM.Resources.Dashborad.jpg

@asutosh said:

i have installed the WLSDM and set the java option as well. WLSDM console and agent loaded successfully.

But i am getting error when saving all monitoring setting

####<13-Mar-2018 13:50:16 GMT><Unparseable date: “-- 23:59:59”

java.text.ParseException: Unparseable date: “-- 23:59:59”
at java.text.DateFormat.parse(DateFormat.java:366)
at com.wlsdm.J.F.H(Unknown Source)
at com.wlsdm.J.D.hasLicense(Unknown Source)
at com.wlsdm.H.a$_A.run(Unknown Source)
at java.lang.Thread.run(Thread.java:748)

Please suggest how can we fix this

Hi,
wlsdm.log is available in $DOMAIN_HOME/WLSDM/logs folder. Just zip the whole folder and upload it. We will help you by investigating the real problem.
Regards…

Hi,

“Thread Dump Analyzer” requires to full thread dump for analyzing.

Normally WLSDM gets a full thread dump. But if there is an exception, like in your case (connection timeout); by default, WLSDM tries to get it using WebLogic API. And sometimes WebLogic does not provide a full thread dump.

That’s why you didn’t get a full thread dump even your managed WebLogic server has a WLSDM agent.

Thanks.

@hmurali said:

@wlsdmsupport Thanks for the update.

Do we also get alerts when the server health goes to warning/overloaded state and Server state goes to ADMIN/UNKNOWN status.

Kindly advise.

Thanks
Hari

Hi Hari,
Additionally please check this tutorial to find out and learn more: https://www.youtube.com/watch?v=PeKJusLuarI
Regards…

Hi @jorfergo,

The current WLSDM release doesn’t support this feature.

Please add your exact requirement on this topic: http://community.wlsdm.com/topic/18/wlsdm-new-features-requests

We will implement in the next release if our analyze team approve.

Regards.

Hi,

We are not supporting multiple log files (types) for a query/monitoring.

So currently you should repeat the monitoring queries.

But, you can assign the query to multiple servers for the “ServerLog”, “stdOut”, “stdErr” and “Diagnostic Log” types.

Kind Regards.

@catgovind said:

Thank you so much. It is working perfectly.

We will add additional NOTE to WLSDM readme in the next release. Thank you for reporting it.

Regards…

Hi,

WLSDM doesn’t support the multiple log files for log monitoring.

The current algorithm based on, “one log file, one search string” rule.

So, currently, there is no easy way to do this.

But we are going to report your request for the next WLSDM version.

Hi,

ProcessCPULoad metric values are sets between (zero) 0 and (one) 1 as “java.lang.Double” by the JVM.

So “1” means 100%.

To get an alert (for testing purpose), you should set the threshold value to less than “1”. eg. “0.01” (1%)
3.png

Hi,

We are not supporting multiple log files (types) for a query/monitoring.

So currently you should repeat the monitoring queries.

But, you can assign the query to multiple servers for the “ServerLog”, “stdOut”, “stdErr” and “Diagnostic Log” types.

Kind Regards…

Hi,

“[email protected]” is default sender (from) address for WLSDM and your mail client may not accept it.

To change sender address:

• Go to “Configuration > WLSDM System Settings” page
• Select the “mail.account” tab
• Edit the “mail.account.smtp.username” property (e.g. [email protected])

settings.jpg

Test changes :
On “Configuration > WLSDM System Settings” page; open “Page Operations” menu and click “Test Email Settings” button

poperations.jpg

testmail.jpg

Hi,

The right side of equal char which is attributeValue must be only numeric values.Probably your script contains string and you need to trim string chars.

Also the first “/” should be replaced, too. Here is sample blog for your reference. One of our community user; used below script for doing it.

http://mathiassalgado.blogspot.com/2017/06/add-metric-options-to-devops-mbean-with-wlsdm-weblogic-console.html

script→ df -H | grep -vE ‘^Filesystem|tmpfs|media’ | awk ‘{ print $6"="$5}’ | sed ‘s/%//’ | sed ‘2s///ROOT/’ | sed ‘s///_/g’

I recommend filter the result set; it does not make sense to use every result for “df –h” . i.e. you /etc, /dev, proc, system… Only consider the mount points which relevant with WebLogic JVM processes.

Regards…