includes/definitions/fujitsueternusos.yaml

os: fujitsueternusos
text: 'Fujitsu ETERNUS'
type: storage
icon: fujitsu
mib_dir: fujitsu
over:
    - { graph: device_bits, text: 'Device Traffic' }
    - { graph: device_processor, text: 'CPU Usage' }
    - { graph: device_mempool, text: 'Memory Usage' }
discovery:
    -
        sysObjectID:
            - .1.3.6.1.4.1.211.1.21.1.150
newdevice: Basic Fujitsu DX Support #5260 2017-01-01 18:18:11 +02:00			`os: fujitsueternusos`
Updated YAML schema validation (#8808) Changed some values to be explicitly boolean DO NOT DELETE THIS TEXT #### Please note > Please read this information carefully. You can run `./scripts/pre-commit.php` to check your code before submitting. - [x] Have you followed our [code guidelines?](http://docs.librenms.org/Developing/Code-Guidelines/) #### Testers If you would like to test this pull request then please run: `./scripts/github-apply <pr_id>`, i.e `./scripts/github-apply 5926` 2018-06-15 03:45:20 -05:00			`text: 'Fujitsu ETERNUS'`
fix: Fix some YAML formatting (#7544) 2017-10-25 14:22:06 +02:00			`type: storage`
newdevice: Basic Fujitsu DX Support #5260 2017-01-01 18:18:11 +02:00			`icon: fujitsu`
Improve mib_dir setting consistency (#12069) yaml os discovery now respects the os mib_dir definition mib_dir now only allows strings, not arrays changed schema validation to account for that consolidated dell mibs, no reason for them to be spread out 2020-09-08 05:55:29 -05:00			`mib_dir: fujitsu`
newdevice: Basic Fujitsu DX Support #5260 2017-01-01 18:18:11 +02:00			`over:`
			`- { graph: device_bits, text: 'Device Traffic' }`
			`- { graph: device_processor, text: 'CPU Usage' }`
			`- { graph: device_mempool, text: 'Memory Usage' }`
refactor: Moved simple os discovery into yaml config (#5313) 2017-01-06 04:04:30 +00:00			`discovery:`
Reformat OS yaml so it is easier to read 2020-06-25 14:43:53 -05:00			`-`
			`sysObjectID:`
			`- .1.3.6.1.4.1.211.1.21.1.150`