Need Help with Rootcause Analysis for missing Interface historical data

Hello House,

Can anyone help with the possible explanation, why we are missing historical data in our SolarWinds Platform?

One of the nodes being monitored is a Cisco Call Manager. There are directly attached E1 interfaces that were in use throughout the year 2024. In December 2024, we unplugged the E1 cable from the Call Manager device interfaces due to transitioning to a SIP Trunk service. No actions or alteration were performed in SolarWinds.

This month, being July, there was a request to spool the availability report for the E1 interfaces up till December when it was unplugged for an ongoing investigation, but surprisingly, no data was found for the E1 interfaces even when they still exist in the SolarWinds platform.

An investigation of the Data Retention Settings was carried out, and it turns out that they were not altered from the default settings: Daily Statistics was set to 365 days. With this setting, we should have report data for up to five months, but there was nothing returned.

Has anyone experienced this before, or am I doing something wrong?

Please, I need help resolving this issue.

Find more posts tagged with

network_monitoring

network

npm

report

Accepted answers

All comments

vinay.by

The E1 interface that you are referring to is it currently in Unknown state ? Possibly this is the issue, if interface is in unknown state for an extended time it might cause an issue in retrieval of historical data.

eno

Thanks for the response Vinay. I will check and confirm if there was a change on the interface from the device side. Could you also direct me to the actual database table to look at this information?

And, if the interface configuration like name change had happened, is there a way to spool the report referencing the original interface detail? If it is possible, please I will greatly appreciate your support and guide on how to go about it.

Thank you so much.