We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
step to reproduce: $ pminfo -f network.interface.up lists all existing network interfaces and their state
$ pmseries network.interface.up $ pmseries -i .....
shows all network interfaces as instances
connecting by pmlc to the logger and quering the network.interface.up shows all the netwrok interfaces as instances
now, create and activate a new network interface
$ pminfo network.interface.up correctly lists all currently existing network interfaces including the new one.
shows the same instance list as before, missng the new network interface
connecting by pmlc to the logger and quering the network.interface.up shows the new instance but with strange name as "???" (three question marks)
mand on 10 sec [66 or "???"]
But getting the http interface at /metric correctly includes the new network interface
expected behaviour: new interface should be listed by pmseries and should logged.
workround: after restarting the pmlogger service, the new network interface appear in the pmseries command output
tested pcp version: 6.3 and 6.2
comment: new network interfaces may appear frequently on virtual hosts when starting new virtual machines or assingning new interfces to running VMs.
I am not aware of any config option for pmseries to recognize new instances of metrics, so I think it is a bug
The text was updated successfully, but these errors were encountered:
No branches or pull requests
step to reproduce:
$ pminfo -f network.interface.up
lists all existing network interfaces and their state
$ pmseries network.interface.up
$ pmseries -i .....
shows all network interfaces as instances
connecting by pmlc to the logger and quering the network.interface.up
shows all the netwrok interfaces as instances
now, create and activate a new network interface
$ pminfo network.interface.up
correctly lists all currently existing network interfaces including the new one.
$ pmseries network.interface.up
$ pmseries -i .....
shows the same instance list as before, missng the new network interface
connecting by pmlc to the logger and quering the network.interface.up
shows the new instance but with strange name as "???" (three question marks)
mand on 10 sec [66 or "???"]
But getting the http interface at /metric correctly includes the new network interface
expected behaviour: new interface should be listed by pmseries and should logged.
workround: after restarting the pmlogger service, the new network interface appear in the pmseries command output
tested pcp version: 6.3 and 6.2
comment: new network interfaces may appear frequently on virtual hosts when starting new virtual machines or assingning new interfces to running VMs.
I am not aware of any config option for pmseries to recognize new instances of metrics, so I think it is a bug
The text was updated successfully, but these errors were encountered: