#Renaming vServer starts a new instance..

1 messages · Page 1 of 1 (latest)

slow mountain
#

Hi there.
We had to rename a vServer which we did, but sadly harvest sees this a a new vServer... is there a way to rename/combine or delete old vServers and their data?

spice whale
#

@slow mountain With the rename, Harvest will start emitting metrics with the new vserver name, as that's what Harvest now collects from ONTAP. Could you share how you have installed Harvest: RPM, DEB, container, or NABox? Are you using Prometheus, InfluxDB, or VictoriaMetrics?

slow mountain
#

nabox

spice whale
#

And you want to delete the old vserver name because it shows up in the dashboard's dropdown filter or time series panels?

#

NABox uses VictoriaMetrics, so the steps mentioned at VictoriaMetrics should help. However, given that those old vserver metrics will become obsolete over time, you might not need to delete them. You should be careful when deleting metrics, as you only want to delete metrics associated with that old vserver name, which could include several metric names. It's better to try this first in a non-production environment.

Guides: How to delete or replace metrics in VictoriaMetrics

Documentation for VictoriaMetrics, VictoriaLogs, Operator, Managed VictoriaMetrics and vmanomaly

slow mountain
#

It would be ideal if it was possible to rename it and keep the stats...

#

and... how some harvest doesn't use the UUID's of vServers and/or volumes which would "fix" this type of issue?

spice whale
#

@slow mountain The UUID will have similar issues with multiple time series. This is because the vserver name associated with older timestamps will remain unchanged, resulting in the time series displaying the old vserver name for those timestamps. Relational databases are better suited for handling such scenarios.