bharathkumarnec did you find a resolution for this? I'm running into the same issue on AIX 7.1 while attempting to install multiple forwarders.
Works fine on Linux.
... View more
This appears to work:
index=main sourcetype=Metrics MEASUREMENT_POINT_NAME = "Test" ELAPSED_TIME < 1 | eval ELAPSED_TIME=tonumber(ELAPSED_TIME)| stats avg(ELAPSED_TIME)
I'll have to verify the accuracy of it, but it appears to correct. Can you explain why Splunk interpreted this field as non-numeric by default? It should be noted that these events are db inputs from DB Connect2, maybe that has something to do with it?
... View more
I wish it was that straigthforward, but no, all of the values are between 0 and 1 with the exception of a few (which is why I'm trying to filter to just the ones that are less than 1).
If I do stats count(ELAPSED_TIME) I get the correct number of events. But if I do any other function of stats (avg, sum, min, max), I get a result of 0 every time.
... View more
If I run this search:
index=main sourcetype=Metrics MEASUREMENT_POINT_NAME = "Test" | stats avg(ELAPSED_TIME)
I get the expected average.
If I run the following search, I get the expected results of events where the ELAPSED_TIME field is less than 1.
index=main sourcetype=Metrics MEASUREMENT_POINT_NAME = "Test" ELAPSED_TIME < 1
But if I combine the two searches (looking for an average ELAPSED_TIME for events in which ELAPSED_TIME is less than 1):
index=main sourcetype=Metrics MEASUREMENT_POINT_NAME = "Test" ELAPSED_TIME < 1 | stats avg(ELAPSED_TIME)
I get 0 as a result.
What am I missing to achieve the desired results?
Thanks!
... View more
Well I installed the JRE and JDK 8, and now I get this message:
JRE Status: Unsupported JRE detected. Using: IBM Corporation JRE version: 1.0 and VM: IBM J9 VM . Need: Oracle Corporation JRE version 1.8
It's saying IBM version 1.0 now, instead of 1.8 like it did previously... very odd. But I just noticed this in the docs:
Only the Oracle JDK is certified and supported for use with Splunk DB Connect.
I assume this means that IBM's flavor for AIX isn't supported? All the more reason to move off of AIX sooner rather than later, I suppose.
... View more
Thanks for the prompt response! I glazed over that part of the doc since older versions only required the JRE, and on the setup page it specifically asks for the path to the JRE, not JDK. I'll get the JDK installed and hopefully that'll resolve the issue.
Also, we're currently evaluating moving our indexers off of AIX, but in the meantime will be sticking with 6.2.8 until we can vet Linux on PPC or decide to go with RHEL or Windows. It's disappointing that AIX support was removed in 6.3.0.
... View more
Fresh install of Splunk 6.2.8 and latest DB Connect 2. Installed the IBM AIX JRE 1.8
java version "1.8.0"
Java(TM) SE Runtime Environment (build pap3280sr1fp10ifix-20150723_01(SR1 FP10+IV75420))
IBM J9 VM (build 2.8, JRE 1.8.0 AIX ppc-32 20150722_258693 (JIT enabled, AOT enabled)
J9VM - R28_jvm.28_20150722_1718_B258693
JIT - tr.r14.java_20150625_95081.02
GC - R28_jvm.28_20150722_1718_B258693
J9CL - 20150722_258693)
JCL - 20150711_01 based on Oracle jdk8u51-b15
But DB Connect setup gives me this error:
JRE Status: Unsupported JRE detected. Using: IBM Corporation JRE version: 1.8 and VM: IBM J9 VM . Need: Oracle Corporation JRE version 1.8
It has worked previously with this same JRE with an older version of DB Connect and 6.1.x of Splunk. I'm guessing that the error is due to DBX looking for a hard-coded version string, and not actually with compatibility of the JRE. Can anyone help?
... View more