[New Package] Add Juniper JunOS Metrics integration#17791
Open
Oddly wants to merge 1 commit intoelastic:mainfrom
Open
[New Package] Add Juniper JunOS Metrics integration#17791Oddly wants to merge 1 commit intoelastic:mainfrom
Oddly wants to merge 1 commit intoelastic:mainfrom
Conversation
Oddly
force-pushed
the
add-juniper-junos-metrics
branch
from
545ac29 to
f5ac8d3
Compare
ReviewersBuildkite won't run for external contributors automatically; you need to add a comment:
NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details. |
Contributor
Author
|
This integration came from a need to ingest metrics from Juniper. Tried SNMP, but that was no success. This was way easier and a bit more modern. |
Oddly
force-pushed
the
add-juniper-junos-metrics
branch
from
427bffb to
6dfc5da
Compare
Initial release of Juniper JunOS Metrics, a CEL-based integration that collects metrics from Juniper JunOS devices via the REST API. Includes 13 data streams covering route engine, interfaces, interface queues, BGP, OSPF, routing table, storage, environment, alarm, ARP, LLDP, system users, and system information. Ships with three Kibana dashboards for overview, route engine, and interface monitoring.
Oddly
force-pushed
the
add-juniper-junos-metrics
branch
from
6dfc5da to
38e1179
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a new integration that collects operational metrics and alarm logs from Juniper JunOS devices via the REST API. It uses CEL input to poll 12 RPC endpoints per device and produces TSDB-compatible time series data.
13 data streams: route_engine, interfaces, interface_queues, bgp, ospf, routing_table, storage, environment, alarm, arp, lldp, system, system_info
3 Kibana dashboards: Overview, Route Engine, Interfaces
Each data stream resolves the device hostname on first poll and caches it in the cursor. An optional
device_namevariable overrides this for friendly dashboard labels. All data streams unwrapmulti-routing-engine-resultsfor dual-RE systems and include guards for optional API response keys.No namespace conflicts with existing
juniper_junosorjuniper_srxpackages — those collect syslog-based logs, this collects polling-based metrics.Testing
img/time_seriesindex mode with proper dimensions, counters, and gaugesmetric_typeandunitannotations on all applicable fields