You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Problem
Currently our Splunk instance ingests the ...\MSx.log files and parses that to get (among other things) the managed server status (e.g. RUNNING, FORCE_SHUT_DOWN, ADMIN, etc.). The problem is, for example, a server goes to RUNNING status when it's brought up and then the status doesn't change for the next 2 months. Our retention period is only 40 days, so after the retention period expires the status is no longer available to searches. As a result, dashboard indicators start displaying "No results found" instead of the current status.
Request
If I login to the WebLogic admin console and look at the servers, I can see each one has a status - usually "RUNNING." There should be a way for the WebLogic application to poll either the AdminServer or each of the managed servers to ask about their status and report it to Splunk. This would ensure our dashboards always show the current status accurately.
The text was updated successfully, but these errors were encountered:
The Problem
Currently our Splunk instance ingests the ...\MSx.log files and parses that to get (among other things) the managed server status (e.g. RUNNING, FORCE_SHUT_DOWN, ADMIN, etc.). The problem is, for example, a server goes to RUNNING status when it's brought up and then the status doesn't change for the next 2 months. Our retention period is only 40 days, so after the retention period expires the status is no longer available to searches. As a result, dashboard indicators start displaying "No results found" instead of the current status.
Request
If I login to the WebLogic admin console and look at the servers, I can see each one has a status - usually "RUNNING." There should be a way for the WebLogic application to poll either the AdminServer or each of the managed servers to ask about their status and report it to Splunk. This would ensure our dashboards always show the current status accurately.
The text was updated successfully, but these errors were encountered: