The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

As a follow up to this question:

Can a service be made to obey the SADIAGDIR setting?

does any documentation about the contents of sadiags.xml exists?

The entry maxconcurconn smells like a snapshot of how many clients have connected simultaneous. Nice is also the list of client applications which connected to the server.

asked 06 Jul '11, 02:46

Martin's gravatar image

Martin
8.6k114149237
accept rate: 14%

1

It's XML - and by design self-documenting, isn't it:)

(06 Jul '11, 04:29) Volker Barth

Martin: There is no documentation on the contents of this file. The servers (ML, SA, ...) update the file with various statistics each time the server is shutdown and each day around midnight. The file consists of a set of "counters" that are incremented at certain times - exactly when is dependent on what the counter is counting. The data is "aged" so that each counter has a count for each day (for the past 14 or so days) and each month (for the past ? months). The base date is maintained at the beginning of the file.

The intent of the collected statistics are:

  • to help SA engineers understand how the server was being used when looking at crash reports and/or tech support cases
  • to help SA engineers and product management understand how and what features are being used so that we can make the product better in future releases.

HTH

permanent link

answered 06 Jul '11, 08:07

Mark%20Culp's gravatar image

Mark Culp
22.3k9129262
accept rate: 40%

edited 06 Jul '11, 08:09

If you have a question about any particular counter and/or section, post a comment here stating which counter/section you would like to know about and I will try to give you an explanation of what it counts.

(06 Jul '11, 08:56) Mark Culp
1

"maxconcurconn" (full path sa/db/comm/maxconcurconn) records the maximum concurrent client connections that was seen during the database server's up-time. The counter gets recorded/saved only when the server shuts down normally (note: I'll need to fix that - most counters also get recorded when an abnormal shutdown/crash occurs but this "one shot" counter - since it is a "max" counter and hence does not know which counter to increment until the end - is (currently) only incremented during the normal shutdown sequence).

(06 Jul '11, 09:10) Mark Culp
Replies hidden

so it is not updated during midnight?

(06 Jul '11, 11:38) Martin
1

The current implementation in released software will not update the maxconcurconn counter at midnight.

(06 Jul '11, 11:58) Mark Culp

Is there any way to tell the server not to create this file? Or to create it somewhere else. Our deployment does not create the SADIAGDIR variable, and i would like to avoid creating such variables.

permanent link

answered 21 Oct '11, 04:53

Sergio's gravatar image

Sergio
460151820
accept rate: 0%

You should post this as a new question... because that's what it is... it's not an answer or a comment on this question.

(21 Oct '11, 06:37) Breck Carter
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×11

question asked: 06 Jul '11, 02:46

question was seen: 1,625 times

last updated: 21 Oct '11, 06:37