I am absolutely not familiar with WebSphere and haven't found anything about this within the last 30 of minutes web research.
Is there a view where i can obtain a list of server events such as starts-, stops- or restarts in the web console of a WAS 8.5 application server?
What i tried:
30 Minute Web research.
My workaround :I always used our Splunk to filter for example "Starting Application..." to identify the time a Application was started based on the log events. I apply similar filters to recognize server restarts.
By default there is no such view. There are at least 2 potential solutions, that you could use, but your workaround might be easier ;-) :
Enable Runtime Messages
In the web console go to Troubleshooting > Runtime Messages > Runtime information.
Enable Info level, save and restart. Then you will be able to filter massages using filter in the table and providing message fragment.
Use HPEL logging and filtering
You can switch default logging to HPEL in the Logging and tracing > server1 > Switch to HPEL. After that your logging will be done in binary form (much better performance) and you will be able to do searches based on the event code, message content etc. You will be able to view log either from the console Logging and tracing > server1 > JVM Logs > Runtime with search/filtering capability, or from command line using logviewer tool. Tool can be used a bit like tail/grep combination and print only relevant information or information from specified application. In this case you will also be able to view past events also, as in Runtime messages you see only events from server startup.
Custom MBean listener
You could write code to listen on events generated by the server, but probably too much effort for your need.
See also:
Runtime events
HPEL overview
LogViewer tool
Related
I am using intellij idea to run the project
java version 17
spring boot project build is succeeded.
but when I am start to run the project in Debug mode it takes since 2 hours.
I have tried to add application.properties file by added the below line
logging.level.org.springframework.boot.autoconfigure=DEBUG
Why do you think it shouldn't be like this?
It's a SpringBoot application that is basically a web server with HTTP endpoints. Those endpoints listen for user requests using a number of threads. E.g. StackOverflow runs their own web server (many of them) to serve many many user requests like yours and mine. For that to work, those web server processes must always be active (up and running). The same is with your application.
You can dive a bit deeper and see what your application threads are actually up to. To do that you should click "Get Thread Dump" button. Looking at your screenshot I believe you should click the double arrow icon in the bottom left corner and then you will see the photo camera logo. This is the one you should click to take the thread dump. Mine looks like this:
You can see at least 2 threads are responsible for handling HTTP requests. You will have a similar picture.
Also, it has nothing to do with Debug mode. You can do the same in the Run mode. The logging.level.org.springframework.boot.autoconfigure=DEBUG option is just for logging, as the name implies. This is why you can see some Spring AutoConfiguration info in the IDE console. For example, if I run my similar SpringBoot app without that option set to DEBUG I will only see the following in the console (spot the default INFO logging level):
I am running a job on my Heroku app that generates about 300k lines of log within 5 minutes. I need to extract all of them into a file. How can I do this?
The Heroku UI only shows logs in real time, since the moment it was opened, and only keeps 10k lines.
I attached a LogDNA Add-on as a drain, but their export also only allows 10k lines export. To even have the option of export, I need to apply a search filter (I typed 2020 because all the lines start with a date, but still...). I can scroll through all the logs to see them, but as I scroll up the bottom gets truncated, so I can't even copy-paste them myself.
I then attached Sumo Logic as a drain, which is better, because the export limit is 100k. However I still need to filter the logs in 30s to 60s intervals and download separately. Also it exports to CSV file and in reverse order (newest first, not what I want) so I have to still work on the file after its downloaded.
Is there no option to get actual raw log files in full?
Is there no option to get actual raw log files in full?
There are no actual raw log files.
Heroku's architecture requires that logging be distributed. By default, its Logplex service aggregates log output from all services into a single stream and makes it available via heroku logs. However,
Logplex is designed for collating and routing log messages, not for storage. It retains the most recent 1,500 lines of your consolidated logs, which expire after 1 week.
For longer persistence you need something else. In addition to commercial logging services like those you mentioned, you have several options:
Log to a database instead of files. Something like Apache Cassandra might be a good fit.
Send your logs to a logging server via Syslog (my preference):
Syslog drains allow you to forward your Heroku logs to an external Syslog server for long-term archiving.
Send your logs to a custom logging process via HTTPS.
Log drains also support messaging via HTTPS. This makes it easy to write your own log-processing logic and run it on a web service (such as another Heroku app).
Speaking solely from the Sumo Logic point of view, since that’s the only one I’m familiar with here, you could do this with its Search Job API: https://help.sumologic.com/APIs/Search-Job-API/About-the-Search-Job-API
The Search Job API lets you kick off a search, poll it for status, and then when complete, page through the results (up to 1M records, I believe) and do whatever you want with them, such as dumping them into a CSV file.
But this is only available to trial and Enterprise accounts.
I just looked at Heroku’s docs and it does not look like they have a native way to retrieve more than 1500 and you do have to forward those logs via syslog to a separate server / service.
I think your best solution is going to depend, however, on your use-case, such as why specifically you need these logs in a CSV.
I am trying to make Grafana display all my metrics (CPU, Memory, etc).
I have already configured Grafana on my server and have configured influxdb and of course I have configured Jmeter listener (Backend Listener) but still I cannot display all grpahas, any idea what should I do in order to make it work ?
It seems like that system metrics (CPU/Memory, etc.) are not in the scope of the JMeter Backend Listener implementation. Actually capturing those KPIs is a part of PerfMon plugin, which currently doesn't seem to support dumping the metrics to InfluxDB/Graphite (at least it doesn't seem to work for me). It might be a good idea to raise such a request at https://groups.google.com/forum/#!forum/jmeter-plugins. Until this gets done, I guess you also have the option of using some alternative metric-collection tools to feed data in InfluxDB/Graphite. Those would depend on the server OS you want to monitor (e.g. Graphite-PowerShell-Functions for Windows or collectd for everything else)
Are you sure that JMeter posts the data to InfluxDB? Did you see the default measurements created in influxDB?
I am able to send the data using backend listener to influxdb. I have given the steps in this site.
http://www.testautomationguru.com/jmeter-real-time-results-influxdb-grafana/
I am using WebSphere 6.2 and my requirement is I admin have to get an alert when the application on the server stopped or server down .. How to achieve this ? In higher versions this feature is there ? please help me
Thanks in Advance ,
Raj
I'm assuming you mean WebSphere application server processes (rather than the physical server on which WebSphere is running) and individual applications running on those processes. I'm also assuming you mean when those elements have stopped unexpectedly rather than when somebody has deliberately stopped them.
If so, you're going to have to use external monitoring software to detect most of those conditions. We use a combination of scripts that scan for processes and specific error messages in logs and external site-monitoring software that checks for application responsiveness. Such scripts can be standalone, handwritten scripts, or run under generic monitoring tools from IBM (Tivoli) or 3rd-parties.
Alternatively, I think you should also be able to write something that uses JMX to read specific things about WebSphere state, and there is at least one sophisticated monitoring tool you could purchase, IBM Tivoli Composite Application Manager (ITCAM) for Application Diagnostics, which can monitor WebSphere internals.
I'm digging into Java EE for the first time in years. I'm looking for recommendations on Java EE debugging and monitoring tools. I'd like to find a tool that lets me dynamically explore the threads space etc.
I'm primarily working with Tomcat. update: and Java 5. (Rats.)
If you are unable to use VisualVM (not sure how it plays with Java5 instances), take a look at Lambda Probe.
Lambda Probe may not have all of the features you want (e.g. threads), but does have quite a few monitoring features and works with Java 4 and 5.
New! Comprehensive JVM memory usage monitor.
JBoss compatibility
Display of deployed applications, their status, session count,
session object count, context
object count, datasource usage etc.
Start, stop, restart, deploy and updeploy of applications
Ability to view deployed JSP files
Ability to compile all or selected JSP files at any time.
Ability to pre-compile JSP files on application deployment.
New! Ability to view auto-generated JSP servlets
Display of list of sessions for a particular application
Display of session attributes and their values for a particular
application. Ability to remove
session attributes.
Ability to view application context attributes and their values.
Ability to expire selected sessions
Graphical display of datasource details including maximum number of
connections, number of busy
connections and configuration details
New! Ability to group datasource properties by URL to help
visualizing impact on the databases
Ability to reset data sources in case of applications leaking
connection
Display of system information including System.properties, memory
usage bar and OS details
Display of JK connector status including the list of requests
pending execution
Real-time connector usage charts and statistics.
Real-time cluster monitoring and clulster traffic charts
New! Real time OS memory usage, swap usage and CPU utilisation
monitoring
Ability to show information about log files and download selected
files
Ability to tail log files in real time from a browser.
Ability to interrupt execution of "hang" requests without server
restart
New! Ability to restart Tomcat/JVM via Java Serview Wrapper.
Availability "Quick check"
Support for DBCP, C3P0 and Oracle datasources
Support for Tomcat 5.0.x and 5.5.x
Support for Java 1.4 and Java 1.5
The state-of-the-art is probably VisualVM.