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
    • Empower Replay: Limited Edition
    • 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
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • DataMiner Insights
      • Security
      • System Architecture
      • DataMiner Releases & Updates
    • 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)
    • DataMiner DevOps Professional Program
  • Downloads
  • More
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
      • General Inquiries
      • DataMiner DevOps Support
      • Commercial Requests
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Visual Overview – Collecting a trend graph from a specific element in a service

Solved1.68K views18th November 2022Parameters shape data trending Visio Visual Overview
1
David Pernes [SLC]90 3rd August 2021 1 Comment

I'm facing a possible Visual Overview issue when collecting trend data from a parameter of an element inside a service.

I'm assigning a Visio drawing to a service.
This service holds a few elements that capitalize on the Alias feature.
I want make sure my drawing can be re-used by multiple services that may or may not have the same elements inside.
On the following picture you can see 3 use cases of the same trend graph.
To provide string visibility of the "Parameters" shape data, I replaced the '[]' for '()'.

  1. Static Element ID | Static Key 

The Element ID and the Key are fixed. This works but I would need to create a Visio drawing for each service, which is not practical.

2. Static Element ID | Key collect from Resource DVE

Also not an option due to having static element ID.
For some reason the "green" alarm state is not reflected for the same data as in use case 1.

3. Dynamic Element ID | Key Collect from Resource DVE

In this case everything is dynamic so this Visio drawing could work for any service I apply it to.
The problem is that it is not working. I suppose the problem might be related with the first segment of the Parameters shape data because when I set it to a fixed value like 620/18672, data becomes available.
Also tried to add the ServiceContext shape data to narrow down the filtering possibilities but no positive outcome.

Stefan Schedletzky [DevOps Enabler] Posted new comment 18th November 2022
Stefan Schedletzky [DevOps Enabler] commented 18th November 2022

I have a similar situation. But what I don’t understand is, why is the wildcard for an element not working? If you just display a parameter it’s working but the trend component isn’t working.

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
1
Emmanuel Dal [SLC] [DevOps Member]4.63K Posted 3rd August 2021 1 Comment

As alternative, and considering your service contains child items from different protocol drivers, you can create containers to generate shapes for each item of the service and filter based on protocol (see help section )

That way, your container will only generate one shape for the child Element matching the protocol you specify in ChildrenFilter.

David Pernes [SLC] Posted new comment 5th August 2021
David Pernes [SLC] commented 5th August 2021

Suggested solution worked.
Implemented a 3 layer shape.
1. Layer Properties:
Children: Element

2. Layer Properties:
ChildType: Element
ChildrenFilter: Amazon AWS Elemental MediaLive.MediaLive Channel // Function DVE Protocol Name

3. Layer Properties:
Element: *
Component: Trending
Parameters: [sep::$]3104$[param:*MediaLive Channel*,3001]:0

You are viewing 1 out of 2 answers, click here to view all answers.
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

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin