Skip to content
DataMiner Dojo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Program
    • DataMiner DevOps Support
    • Feature Suggestions
  • Downloads
  • Swag Shop
  • PARTNERS
    • Business Partners
    • Technology Partners
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Preserve trending when DVE gets re-created

60 views23 hours agoDVE historical trending trending
5
Arunkrishna Shreeder [SLC] [DevOps Enabler]4.22K 1 day ago 0 Comments

Hello,

We have a parent element and its DVE(s) to monitor a device and its sub-devices.

Sometimes, one of the sub-devices get broken and need to be manually replaced.
Due to this, the old DVE is correctly discarded by DataMiner and we manually have to re-create a new DVE to monitor the new sub-device.

The problem with this approach is since the new DVE is similar to a new element, it does not contain the trending the old DVE had – this results in a loss of continuity when viewing historical data as the new DVE does not contain historical data.

The sub-device however retains the historical trending when viewed from the sub-device GUI.

Is there any way to work around this ? How can I ensure the new DVE gets access to the historical trending the old DVE had ?

Thanks in advance.

Miguel Obregon [SLC] [DevOps Catalyst] Answered question 23 hours ago

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
3
Miguel Obregon [SLC] [DevOps Catalyst]22.12K Posted 23 hours ago 0 Comments

Hi Arun,

As far as I know, the only possible option is to handle this use case in the connector. Instead of removing the old DVE, the connector can verify if the new device is from the same type.

For example, if the parent element is a chassis, most of the time the DVE is identified by the slot number. When a card is replaced, the new card is typically placed in the same slot, which makes the detection straightforward.

However, this approach can introduce corner cases. What happens if the new device has a different identifier than the one being replaced? How the connector can detect that the new device is an actual replacement?

Hope it helps.

Miguel Obregon [SLC] [DevOps Catalyst] Answered question 23 hours ago
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2026 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs