----- "Max Matveev" <makc@xxxxxxxxx> wrote:
> Hi folks,
>
> I've got an interesting pmns problem I'm trying to resolve: I have a
> pmda which, depending on the installation, serves different
> metrics. The metric list is defined by the namespace which gets
> installed with some metrics appearing in all installations and others
> only in some.
>
> ...
>
> The best I've managed to come up so far is to effectively take over
> the pmns and help processing from the PMDA shell library, combine
> pmns
> using explicit cpp run in Install script, do my own help compilation
> and lie to the Install script about the help source to stop it from
> messing with my prepared help.dir/help.pag.
>
> Does anyone has a more elegant solution?
Not for a traditional C agent.
The Perl PMDA module generates the namespace "on the fly" at Install
time, its got the most "dynamic" handling of names of anything I'm
aware of. The MMV PMDA recently (today) acquired some more dynamic
name handling code, too - its now handling arbitrary depth names and
also all on the fly (runtime too, not just Install time).
cheers.
--
Nathan
|