MRTG configuration(s) when deleting or modifying via GUI

[TBT]

While using Nagios XI to modify a Network Element the changes are not reflected in the configuration files.

Additionally, when deleting an element the MRTG config and RRD files are also left behind (located in /etc/mrtg/conf.d and /var/lib/mrtg/). This has caused our organization several unnecessary support requests over the years (dating back to 2011). Manual administration has become quite the task , especially across several XI hosts. Can we please put the wheels in motion to have these maintenance issues more elegantly addressed within the interface?

Looking forward to a resolution, thank you.

[cdienger]

To your first point, what network element are you changing and which file do you expect to see that change in?

To the second, this is currently appears to be a feature request. I've pinged dev regarding it to get more details.

[TBT]

To your first point, what network element are you changing and which file do you expect to see that change in?

To the second, this is currently appears to be a feature request. I've pinged dev regarding it to get more details.

1. More specifically, if an interface with bandwidth monitoring is deleted though CCM, the changes are not reflected in the corresponding config file (eg: /etc/mrtg/conf.d/192.168.1.1.cfg)

2. Yes, please do. This has been long outstanding.

[cdienger]

Both of these have been raised on FR #6503

[TBT]

Both of these have been raised on FR #6503

Please define "raised", does this mean a priority change? Also, I do not see #6503 on Nagios Tracker.

[cdienger]

I brought the issues to the the attention of our dev team and the case has been assigned an internal ticket number of 6503. I included the internal ticket number mainly for the benefit of other techs that may need to look at this thread.

[TBT]

I brought the issues to the the attention of our dev team and the case has been assigned an internal ticket number of 6503. I included the internal ticket number mainly for the benefit of other techs that may need to look at this thread.

Okay.

As I've indicated, these issues have been long outstanding. What is the status of the preexisting ticket you mentioned in your initial reply?

Thank you,

[cdienger]

An initial fix didn't work out so well and we're still investigating to find a final fix.

[TBT]

Hoping to get an update and resolution in 2020, can anyone chime in on the status of this?

[cdienger]

The case is still open but I do not have an ETA.