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

Default Trend behaviour: N/A or Exception Values -VS- TimeOut Gaps

Solved117 views5 days agoadl2099 exception values Trend Graphs Trending monitoring vertical line
1
Alberto De Luca [DevOps Enabler]4.99K 2nd September 2025 0 Comments

Hello Dojo,

I'm looking for a clarification in terms of trend behaviour normally implemented in DM connectors: when is a vertical line added in trend graphs between values?

Typically, if an element is in timeout, a gap is presented in trend graphs as no data was being polled for the
duration of the timeout (No line connecting the discontinuity, this is well known and expected behaviour in DM).

At times, a "Not Available" (typically "-1" mapped as "Not Available") can be defined
e.g. in case a process disappears: would this present the same gap as a timeout (no vertical line)?

Or would this need to produce a vertical line down to a "Not available" on the Y-axis?

Asking in the context of "exception values" too, e.g. all those values that any polled device can use to signal a state that is not a valid measurement, such as:

  • Large constants used as “out-of-range” placeholders

    • 9999, 65535, 2147483647, -999

  • Special strings

    • "N/A", "Not Available", "Invalid", "Unknown"

  • Hex values

    • 0xFFFF (often used in SNMP MIBs to indicate no value)

Trying to streamline the behaviour for different connectors & cases from different vendors - any steer will be helpful.

Alberto De Luca [DevOps Enabler] Selected answer as best 5 days ago

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
Paulo Henriques [SLC] [DevOps Advocate]861 Posted 12th September 2025 3 Comments

Hi Alberto,

My understanding is that whenever the trended parameter changes to one of its exception values (e.g., N/A, -999, 0xFFFF, etc., as defined in the protocol), this change is treated as a discontinuity, and therefore no vertical line is expected.

This seems consistent with your second graph: note that the vertical line indicated by the green arrow represents a transition between normal values, which is different from the transitions to or from N/A.

That said, it’s possible I didn’t fully capture your point—please correct me if I misunderstood.

Paulo Henriques [SLC] [DevOps Advocate] Posted new comment 4 days ago
Alberto De Luca [DevOps Enabler] commented 15th September 2025

Thanks for your feedback Paulo – it makes sense now – so I'd have a vertical line only when there is a transition across normal values.

In case of discontinuity (no vertical line), what is the default behaviour for connectors?

Should a horizontal "gap" be always present in case of element timeout?

Asking to be able to tell the difference between an "exception value" discontinuity VS a timeout discontinuity.

Alberto De Luca [DevOps Enabler] commented 5 days ago

Marking this as solved, Paulo

I've posted the follow-up question here:

https://community.dataminer.services/question/trending-engine-behaviour-exception-values-vs-timeout/

Thanks

Paulo Henriques [SLC] [DevOps Advocate] commented 4 days ago

Hi Alberto,
I read your previous comment and your last question but I'm still trying to find what is the current behavior versus what is expected. Good that you put the question on a new post, it will get a better visibility I think.
Thanks.

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