-
Notifications
You must be signed in to change notification settings - Fork 13
Processor plugin should not create new metrics #29
Comments
This is the behavior of a processor. It shouldn't expose what was collected, but the added value of the collector. If you want to expose collected metrics AND processed statistics: {
"version": 1,
"schedule": {
"type": "simple",
"interval": "1s"
},
"workflow": {
"collect": {
"metrics": {
"/intel/psutil/load/load1": {},
"/intel/psutil/load/load5": {},
"/intel/psutil/load/load15": {}
},
"process": [
{
"plugin_name": "statistics",
"publish": [
{
"plugin_name": "file",
"config": {
"file": "/tmp/published_statistics.log"
}
}
]
}
],
"publish": [
{
"plugin_name": "file",
"config": {
"file": "/tmp/published_psutil.log"
}
}
]
}
}
} |
This is not usual that processor plugin creates new metrics. I don't see in documentation information about it. If I'm right then this information should be added to documentation with clear examples. |
HI! kindermoumoute, Could you please help me with this. Thanks, |
@PraveenkumarDonga Metrics, which you mentioned, are created by processor plugin so probably this is the reason why you don't see metrics using Please check what is saved in |
Hi! Can we store these processed metrics into mongodb again. Thanks, |
@PraveenkumarDonga Please make sure that you have "process": [
{
"plugin_name": "statistics",
"publish": [
{
"plugin_name": "file",
"config": {
"file": "/tmp/published_statistics.log"
}
}
]
}
], |
Processor plugin should not create new metrics
Now after processing there are metrics with namespaces in following forms:
but collector plugin exposes following metric:
The text was updated successfully, but these errors were encountered: