While using stand-alone exporter, keeping target database's credential in the config files may be restricted for some clusters. Are there any ways to identify schema changes other than connecting to the database using native transport protocol?
JMXHarvester doing refresh of MBean for every 30 minutes which will take care of reloading the MBeans of new tables and removal of MBeans of deleted tables.
While using stand-alone exporter, keeping target database's credential in the config files may be restricted for some clusters. Are there any ways to identify schema changes other than connecting to the database using native transport protocol?