monitoring activity with specific p4 repo path or IP?

[evbo]

The readme lists "ip" monitors. What IP are those in reference to?

Is there any suggestions for how this tool can be used to track submit, etc activity for a specific p4 path? I would like to know how frequently engineers are making changes to specific projects, similar to Github's "pulse": https://github.com/perforce/p4prometheus/pulse

This helps track when work is winding down and a release may be ready.

Any suggestions?

[rcowham]

The biggest challenge here is the definition of a project or path or set of paths of interest, and how to keep it up-to-date.
Different repositories have vastly different structures. Many use local depots which are very flexible which has it's own set of challenges. Even with streams, some organisations have a mainline per project, others define different projects for sub-streams.

[rcowham]

Note that IP means the source IP for user commands as found in server log.
Perforce server info: 2015/09/02 15:23:09 pid 1616 robert@robert-test 10.1.2.3 [p4/2016.2/LINUX26X86_64/1598668] 'user-sync //...'
For more than a few users, you probably don't want to track by IP...
Can lead to metric/label cardinality explosion otherwise!

[evbo]

Many use local depots which are very flexible which has it's own set of challenges.

In the simplest case, could we gather metrics grouped by local depot (port) and some pattern of paths (maybe first few folders deep)? What would that look like for the quickest and dirtiest implementation?

Example, depot port 1909 has the following hierarchy:

design/impl/circuit
design/impl/layout
design/impl/gerber
other/...

There could be hundreds of subpaths below those three, but is there a way to sum them under each of those 3? And any paths with activity that don't fall under those folders just get ignored or counted under "other"?

Then our metrics for sum of all submit activity would be the following groups:

{port=1909, path=sch}
{ port=1909, path=layout}
and so on...

[evbo]

So is there no way to track metrics for a fixed or regex local depot path?

[evbo]

@rcowham just curious if you give a basic example for how to count metrics for p4 commands run a specific, hard-coded (or aybe regex) local depot path?