Hello,
We have Upgraded splunk 6.5.4 to 7.2
Splunk version --> 7.2
APP --> NMON Performance by Octamis 1.9.18
Problem --> APP NMON Performance by Octamis on splunk 7.2 when analyse solaris servers impossible dispaly data/graphique
Error --> "XML dashboard scan error: sequence of URI malformed Click on "Edit changes" to correct ".
Our splunk 6.5.4 version had APP NMON Performance by Octamis 1.9.5 version and functioned correctly, but when we have upgrade splunk, this application generate a XML parsing error, howewer we have downgrade nmon app on 1.9.5 and 1.9.17 version the problem is still here.
The problem of interpreting the XML by splunk of the NMON application or the NMON application that is not adapted to splunk 7.2 for the analysis part of solaris servers
We have find a solution for bypass bad scan XML in NMON ANALYSER --> SOLARIS SYSTEM -->dashboard 'NMON Analyse Solaris'
when we are in nmon app menu:
- clic NMON analyser --> SOLARIS SYSTEM --> dashbord : NMON ANALYSER SOLARIS not appear and error display '"XML dashboard scan error: sequence of URI malformed Click on "Edit changes" to correct ".
- clic NMON analyser --> LINUX SYSTEM --> dashboard NMON ANALYSER LINUX appear and filster os have 'ANYS OS' and 'LINUX', url = https://splunk//application/nmon/Nmon_ANALYSER_LINUX?form.df_storage_monitor_unit=pct&form.timerange..., look 'osfilter=Linux'
if you change 'Linux' by 'Solaris' this all servers SOLARIS appear with their graphique. but it indicated that we are always in dasboard NMON Analyser LINUX.
Solaris servers are accessible, but not the right way
users have already had this problem?
Best regards
Thank you for your help @guilmxm, the new version resolve the problem 🙂
Thank you guilmxm for information !
app NMON 1.9.19 version, solve the problem !! 🙂
Please upgrade to version 1.9.19 available in Splunk Base.
Make sure you clean any local version of the dashboard, or any other changes you would have made.
If you issue is fixed, please tag this as answered.
Notes: Have a look at the newest version which relies on the metric store: https://splunkbase.splunk.com/app/3947/
Hi @userk
Thank you for sharing the issue, I just tested it on a fresh instance and there is indeed an error in the dashboard.
Stay tuned, will be corrected like an HF18 bro.
Guilhem