Thanks…

Hi,

This timeout value is a precaution to protect the system.

That’s why we can’t let the increase the timeout value by users.

If you need a long-running process; you can trigger your WLST script using a shell command.

That will cause an immediate return for the main process (Shell Script) but not for the child process (Triggered WLST Script).

Also, this type of usage means; The script is out of the control to WLSDM.

Kind regards.

Hi,

You can’t call the stored WLST scripts from the scheduler module.

And you need a shell script (custom action) to run an external WLST script from the scheduler module.

Kind regards.

@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,

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…

Hi,

This is a cache issue.

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

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.

Hi,

“admin@wlsdm” 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…

Problem is resolved by adding username and removing password. Then the WLSDM email SMTP configurations has been setup successfully for WebLogic.

Hi,

Dashboard pages stores only last 24 hours data.

Older data: If the store data is active for the relevant metrics, you can find it on the “Reports> Metric Reports” page.

Thank you.

answer.png

Hi,

We are supporting upgrade from 2.5.2 to 3.1.1.
Consider upgrade steps then your collected data will be kept and you won’t lost any data. But please take a back-up of WLSDM runtime folder which is located under $DOMAIN_HOME/WLSDM while your admin server is shut down.

Hi,

We are not generating JFR files under /tmp folder. WebLogic does this and we’re using the output. So, if you want to redirect to custom folder please use below settings and let us know the result.

Navigate to Enviroment > Server > Server Start. In “Arguments”, add: “-XX:FlightRecorderOptions=repository=/path/to/tmp/” JVM flags then restart WebLogic managed server(s)

We have Thread Dump action. Just activate ThreadDump action for Hoggers or Stuck metrics and then analyze thread dumps by using “Thread Dump Analyser”. If your Administrator good enough you can write your own scripts for detecting deadlocks on JVM threads.

Normally, WLSDM stores 24 hours data storage for MBeans and backend usage by default. But, all chart values can be stored on WLSDM database by turning it on. You can turn on “Store Data” for every data while setting up WLSDM wizard. After the installation, if you have not turned on “store date”, you need to open them by one by. Good news, you can sort them all on "
• Configuration
• > JMX MBean Metric Browser & Settings” page by sorting “Store Data” column. Just follow notifications on relevant notifications page. They’re stored for three months. Remember we have PURGE and ARCHIVE modules. You do not need to operation your monitoring console. It does everything for you.

StoreData.png

Thank you for your interest. We trust our product very much and we thought every detail for WLSDM.

Here our comments;

First of all, your domain is really big and massive. But, we it is for sure we can handle it.

1 - For my experience what make the difference is collecting data… In order to monitoring historic information anda data (this help me in troubleshooting)
Yes, especially this size of domain is very hard to monitor. If you have any unused server, datasource, JMS definion please delete all, after that fresh resinstall WLSDM and do not track unused apps, servers, deployments… etc.
Historical data would be very useful for your problem troubleshooting. Especially, check notification pages.

2 - About deployments table your dashboard use to list applciation status in evey servers of my cluster and it is a little bit redundat
We have asynchronous backend health feature on health dashboard. Could you please enable it and let us know the result? (Go to Health Dashboard page, > Page Operations Menu> Switch the below button to ON)

save.jpg

By the way, we have JMX/t3 timeout on system.WLSDM tab at System Settings page. If your domain is not responsive has its own problem, we are cutting the request because of keeping WebLogic domain healthy. It’s default value is about 5sec. That’s why you can see the health status conflicts.

We support shell and batch (.sh and .bat/.cmd) OS script execution for custom metric actions. You can trigger any python/jython/wlst script by using WLSDM WebLogic console. We do not support script scheduling because of DevOps support. Scripts triggering is fully parametrical and can be assign to any specific MBean threshold.

WLSDM console runs under WebLogic /console context path. And we’re using default WebLogic security realm. The configuration and important pages on WLSDM console is only accessible for Administrators global role. So, a user which has Monitor global role, only able to see only monitoring pages on WLSDM console. In this case, What kind of requirement do you have for the custom access for accessing WLSDM console.

When we did the webex session we had seen that you are able to login WLSDM console. This situation is something about Webserver. We need to sort out this plain-text problem. Which web server are you using for the redirection for the WebLogic /console redirection? Your web server serving WLSDM console somehow as plain-text instead html. It could be something about mime-type. Could you please check this out and let me see the result? http://stackoverflow.com/questions/9142117/pages-are-displaying-plain-text-instead-of-html

Hi !

WebLogic does not support these file for WLDF querying. Because, there are redirection and broadcast features on WebLogic.

For the .out file Go to “Servers > $SERVER_NAME > Logging (Tab) > General (Subtab)” then enable “Redirect stdout logging enabled” and “Redirect stderr logging enabled”. After the restart you are able to monitor these file by using WLSDM. Write your own WLDF query. If you’re having to define WLDF query please share your log record with us. Then we’ll support you for the relevant WLDF query.

For diagnostic log files WebLogic has broadcast feature for the all log file to broadcast logs to the DOMAIN log file. Go to “Servers > $SERVER_NAME > Logging (Tab) > General (Subtab)” and check “Domain log broadcaster” section and configure your broadcast settings. Decrease buffer size for getting quick results. After that by monitoring Domain.Log you’re able to monitor all kind of files by adding Domain.Log monitoring on WLSDM LogInspector. For the new definition; go to “WLSDM Configuration > Monitoring & Diagnostics > Log Inspector” page and add new from Page Operations menu on WLSDM console.
Hope, this will help you satisfy your requirement.
Could you please, check this solution offer and let us know the result.

Hi,

We support ten different chart types on WebLogic smart dashboards,

We have assigned “Bar” as default type for “ActiveExecuteThread” JMX MBean metric.

Use the “Metric & Chart Options” button at the Chart Panel then you can change the its chart type.

capture1.png capture2.png

The error occurs when serverRuntime is requested …

At javax.management.remote.rmi.RMIConnector $ RemoteMBeanServerConnection.invoke (RMIConnector.java:1020) At weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke (MBeanServerInvocationHandler.java:562) At weblogic.management.jmx.MBeanServerInvocationHandler.invoke (MBeanServerInvocationHandler.java:391) At com.sun.proxy. $ Proxy273.lookupServerRuntime (Unknown Source) At com.wlsdm.L.a.getServerRuntimeMBean (MBSConnection.java:475) At com.wlsdm.frontend.provider.GA.getServerHealthState (PerformanceHealthDatas.java:123) At com.wlsdm.J.O. £ (Data.java:6914)

The WLSDM serverRuntime object is requested via the weblogic console API, and the admin console is also calling managedServers for RMI.

→ Is there any problem on the WebLogic admin console > Servers page? (Just want to diagnose problem)
→ Is there any problem on the WebLogic console in general? Sometimes, network issues can affect WebLogic console and WLSDM console… Please check ConnectionDelayTime on Datasources dashbaord and let us know any sudden increment for this MBean…

Hi there,

It’s possible to redirect std.err and std.out log to “WebLogic Server Logs”. To do this, please follow below procedure.

On WebLogic console, go to “Servers > $Managed_Server_Name > Logging > Advanced” section. Then check below options. (Attached screen capture below)

Redirect stdout logging enabled Redirect stderr logging enabled

upload-6590ce82-e47c-4c88-8e7c-9a7cce2de53d

Then restart relevant WebLogic managed servers. After that, you are able to use “WLSDM LogInspector” as monitoring WebLogic Server Logs. You can write your own WLDF query according to your “stdout” and “stderr” log messages.

@vanrussell_nl

Hi,
this problem only exists on Chrome browser. If your Chrome updated recently, this can be occur. It’s a Chrome issue and we’ve reported.

On WLSDM console refresh page with “CTRL + R” or “CTRL + F5” then it will be resolved.

Regards…

Tags: WebLogic monitoring dashbaord, left main menu

@maas
Hi,
By default WLSDM folder initialize in weblogic $DOMAIN_HOME folder. If you want to move this folder to another path just create soft link.

1- Shutdown WebLogic admin server properly
2- Move $DOMAIN_HOME/WLSDM folder to /path/to/folder/WLSDM
3- Create link under $DOMAIN_HOME folder.
Linux: ln -s /path/to/folder/WLSDM WLSDM