Itziar asked a question.
TIBCO Instance (OS process id) metrics
Hi,
Would anyone who has worked with TIBCO before know how to set up metrics by "Instance" in FNMS for TIBCO Rendezvous products?
As defined by the metrics for TIBCO Rendezvous, "Instance" means a TIBCO Rendezvous daemon or a TIBCO Rendezvous client where each daemon or client is an operating system process with a unique process id.
I would very much appreciate some information on how Flexera collects information on operating system processes.
Thank you very much in advance.
Best regards,
Hi Itziar,
Not exactly with this metric, but here is an idea of what would be needed:
You either find an existing source, like some kind of logging, etc., or you might need to find an external tool to track what you need.
You'll need to come up with an idea how multiple instances are identified and distinguished (process ID?), how the tracking data is processed into something that could be used in FNMS. You could import these as file evidences or installer evidences. But then again, multiple evidences linked to the same app would usually still result in a single installation. So you might need to come up with something more elaborate.
You'll need a way to bring the data into FNMS, likely a business import implementing the logic from above. It should also implement somethign to possibly update existing data and definitely to remove old data. Insert - Update - Delete
Depending on the data and import, you'll need to figure our how FNMS can calculate actual consumption from this. You could go with a distinct application per instance and then have a device license consume per installation. Not sure though, how complex the actual consumption calculation is. It might well be you have to calculate "outside" and then just pass a result to FNMS (e.g. custom metric).This does all not seem to scale very well. You might just ask the publisher how they track these things, like in the case of an audit. Maybe this gives some useful insights.
Best regards,
Markward