BIND 10 #2135: design a new statistics model
BIND 10 Development
do-not-reply at isc.org
Tue Jul 31 09:41:54 UTC 2012
#2135: design a new statistics model
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
naokikambe | Status: reviewing
Type: task | Milestone:
Priority: | Sprint-20120731
medium | Resolution:
Component: | Sensitive: 0
statistics | Sub-Project: DNS
Keywords: | Estimated Difficulty: 8
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by naokikambe):
Replying to [comment:8 vorner]:
> I had a look and I think it is a very bad idea to examine the
Boss/components to count instances of one program. It seems fragile and
could be out of sync. I think we'll need the notifications pretty soon,
but for now, could modules announce themselfs when they appear?
This issue isn't directly related to statistics tasks, I think. If we need
to fundamentally restructure this issue, we don't have enough time until
the end of Sep.. So how about this workaround?
''show_processes'' command of Boss can easily return with address
information of each module. For example,
{{{
#!js
> Boss show_processes
[
[
20056,
"Socket creator",
null
],
[
20057,
"msgq",
null
],
[
20058,
"cfgmgr",
"ConfigManager"
],
[
20059,
"b10-cmdctl",
"Cmdctl"
],
[
20061,
"b10-auth",
"Auth"
],
[
20062,
"b10-stats",
"Stats"
],
[
20103,
"b10-auth-2",
"Auth"
]
]
}}}
In this example, there are two Auth instances. It could be very easy
revision. Can Stats request boss this command for counting instances of
same module? Does that make sense for you?
--
Ticket URL: <https://bind10.isc.org/ticket/2135#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list