Jeff Riechers -GM Posted May 12, 2023 Share Posted May 12, 2023 Well, disregard. I hadn't put .63 in. Once I did that it was fine. Must have been something with .61.So I setup Prometheus and Grafana for testing out metric collections. After updating firmware I no longer have data in Grafana. Going and checking the logs I see the output log file is empty, and in metricscollector.log file I see the following error start ERROR: Invalid schema file : /var/metrics_conf/schema.json: cannot open file Fri May 12 15:21:27 2023start ERROR: Dynamic schema init failed for profile ns_analytics_time_series_profile Check if schema file and file_path is valid!! Fri May 12 15:21:27 2023 The schema file has not changed and looks fine. Link to comment Share on other sites More sharing options...
Jeff Riechers -GM Posted May 12, 2023 Author Share Posted May 12, 2023 Well, disregard. I hadn't put .63 in. Once I did that it was fine. Must have been something with .61. Link to comment Share on other sites More sharing options...
Komal Bhardwaj Posted May 12, 2023 Share Posted May 12, 2023 Hey Jeff, thanks for trying the Prometheus integration capability. Which NetScaler firmware version are you trying ? It should be 13.1-42.47 or later.Secondly, I want to ensure you are trying out the latest documentation - https://docs.netscaler.com/en-us/citrix-adc/current-release/ns-ag-appflow-intro-wrapper-con/prometheus-integration.html. From the error logs it seems, there is some issue either in the schema.json file. Check if there is no comment on the top that starts with /* in this file. Regards,Komal Link to comment Share on other sites More sharing options...
Peter Götze 2 Posted June 22, 2023 Share Posted June 22, 2023 Hi, using 13.1 45.63 but running in the same problem. Any suggestions? No comment strings, schema.json ist the org. Link to comment Share on other sites More sharing options...
GANESH G U P Posted July 7, 2023 Share Posted July 7, 2023 Hi All, please restart metricscollector to overcome this issue <pkill -9 metricscollector>. The fix should be part of the 13.1 49.4 release. Also, this issue happens only if metrics is enabled in AVRO format on any analytics profile. If ADM analytics is not used, please disable metrics on the associated analytics profile.cc @Jeff Riechers @Komal Bhardwaj @Peter Götze Link to comment Share on other sites More sharing options...
Peter Götze 2 Posted July 7, 2023 Share Posted July 7, 2023 Hi Ganesh,upgrade to 13.1 48.47 fixed the problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now