I recently changed my DB Connect 2 connection to point at a new Database. To do this, I created a new Connection with the settings for my new database, and changed my DBInput to use the new Connection.
After making these changes, I can see new data being read from my new connection, however, the Health tab doesn't show any information on this new connection or its transactions.
I thought this could be caused by my changing to use a custom index but I've made that index searchable by default for all users with no luck.
Does anyone know what could be causing this or where I can look for more information?
Additionally, I ran this query from the Health Dashboard:
| tstats dc(All_Records.CONNECTION) from datamodel=DB_Health groupby "All_Records.CONNECTION" | `rename_all`
And it shows only the old connection in there. Is there a way to trigger it to rebuild its datamodel?
DBhealth model search the log based on : sourcetype=dbxhealth index=_internal
You can check if running this search on your indexer to see if new log contains your new connection information. If it does, tstats should pick it up.
Thanks for the pointer. Looking in that search it looks like the connection info is set in
health.py but there hasn't been any events from
health.py since I switched the servers over.
Does this mean that tie
health.py file is no longer being triggered, and if so, how can I restart it?
I checked again today and when I run that search, I can see more recent events, but they still do NOT show up in the Health section.
The one difference I noticed is that the old events in the Health dashboard were logged by [health.py] and contain a connection name, while the newer events were logged by HealthLogger, and do not contain an explicit Connection field.