Hi,
any more ideas how to solve this?
вт, 19 мая 2020 г. в 19:53, Denis Trunov :
> It helped with moduleIDsType metrics - instead of
>
> moduleIDsType{moduleIDsIndex="1"} 296
>
>
> with
>
> overrides:
> moduleIDsType:
> type: EnumAsInfo
>
> I can get
>
> moduleIDsType_info{modul
It helped with moduleIDsType metrics - instead of
moduleIDsType{moduleIDsIndex="1"} 296
with
overrides:
moduleIDsType:
type: EnumAsInfo
I can get
moduleIDsType_info{moduleIDsIndex="1",moduleIDsType="moduleDigitalVideo12PortIO"}
1
But in other metrics I still have
moduleC
On Tue, 19 May 2020 at 16:51, Denis Trunov wrote:
> Hi,
> I have a very simple generator.yml file with just walk section - it works
> fine, I can get metrics look like
>
> moduleConfigsPowerStatus{moduleConfigsIndex="1",moduleIDsType="296"} 2
>
>
> moduleIDsType is described in MIB
>
> moduleIDsT
Hi,
I have a very simple generator.yml file with just walk section - it works
fine, I can get metrics look like
moduleConfigsPowerStatus{moduleConfigsIndex="1",moduleIDsType="296"} 2
moduleIDsType is described in MIB
moduleIDsType OBJECT-TYPE
SYNTAX Integer32 { moduleUnknown(0),
4 matches
Mail list logo