Is the Solution working

Is the Solution working

Now that the hard work is done, complete your installation by running a saved search and check that the views are populated correctly.

Validate that you installed the Solution successfully

Run the setup saved searches:

1. Log into your Splunk Search head.
2. To open the App, choose "WebSphere" in your Home screen.
3. From the App main menu select View > Saved Searches > setup_dropdown.
4. From the App main menu select View > Saved Searches > setup_log
5. If you have installed the Solution correctly you will see a visual representation of the data you are collecting from your WAS environment, with your Deployment Manager, node agents, and app servers listed.
6. Restart your Splunk search head and indexers.

When you run the searches you create the cell_node_server.csv and cell_node_server_log.csv files from your serverindex.xml and server.xml data that was indexed by Splunk. This search populates the filters that show Host, Cell, Node, and Server data on most views. Use the menu options to easily navigate the WAS data in your environment.

To validate data integrity look at:

1. Component Inventory overview: This view verifies that basic config XML data is being collected and indexed by Splunk. Set the Time range to "All Time" to gather an accurate representation of the data.
2. Errors view in the Operations section: Regardless of whether errors are present or not in the specified time range, the Host, Cell, Node, and Server menu dropdowns should populate with your environment. Toggle through the views to ensure that the menus are refreshed and populated correctly. Selecting a Host refreshes the Cell dropdown and populates it with the correct Cell names. Selecting Cell refreshes the Node dropdown and so on.
3. LogEventType=W in the Troublshooting section: Loads all SystemOut.log and SystemErr.log with event type W and ensures JVM log data is being indexed in the websphere index.
4. Server availability in the Operations section: If you have JMX enabled you should be able to see which of your app servers are running. It also establishes whether JMX data is being collected.

Alternatively you can check the JVM Runtime view in the Performance' section, however some of this data may not be indexed and it is determined by your WAS PMI settings in the WAS Admin Console.

• Was this topic useful?
• Post a comment