• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Network Application Monitoring /
  • NAM Open Q&A /
avatar image
Question by Torsten G. · Jun 08, 2015 at 09:12 AM ·

Availability calculation mode (DCRUM 12.1.3)

Hi,

 

I am having an internal discussion in my head I could use some input on.

It is standard in DCRUM 12.1 that TCP connectivity errors are what's included in the calculation for the metric "Availability".

 

I want to change this to "All TCP errors", but how will this affect the Availability metric?

I am not sure if it will use the metric TCP errors to then calculate Availability, or if it will include ALL TCP errors, which would include errors of the type "server session termination errors". In this particular case there is applications using this kind of RESET packets to close TCP sessions (unhealthy and old fashined, but true), so it would completely mess up the statistics if it is included in the Availability metric. Does anyone have any input on this?

 

b.r.

Torsten

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

2 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Torsten G. · Jun 08, 2015 at 12:06 PM

I know, there is no reference to this challenge, and thus it would be nice if someone had some experience with it. 

I did open a ticket on it prior to posting here actually. I can share what ever they come up with of an answer. Note that this is only a problem in 12.1, because the Availability metrics are changed in later versions. 

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Ulf T. · Jun 08, 2015 at 10:37 AM

Hi Torsten

I think that depends on what is included in "All TCP errors" and I can't really tell as I can't find any explicit reference about that.

If for example checksums or retransimissions are considered an error, you might end up with every packet being classified as an error depending on the source of the traffic. I would recommend opening a ticket to get the labs view on what is classified as an error. Please share you findings here (smile)

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Forum Tags

esm siebel Dynatrace Managed license nam probe wan citrix dna rest api configuration mq alerting NAM 2018 dashboard dcrumadvisory reports css nam universal decode database mobileapp RUM ads sap nam console scripting nam server sequence transactions nam 2019 upgrade
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A