# Junos OS

Junos OS: Junos OS is the network operating system for Juniper physical and virtual networking and security products. 

To onboard such a source to Axoflow, complete the [generic appliance onboarding steps](../../../../docs/axoflow/data-sources/appliances/index.md).

## Labels

Axoflow automatically adds the following labels to data collected from this source:

Analytics label | Message field | value  
---|---|---  
`vendor` | [`meta.vendor`](../../../../docs/axoflow/reference/message-schema/reference/index.md#meta.vendor) | `juniper`  
`product` | [`meta.product`](../../../../docs/axoflow/reference/message-schema/reference/index.md#meta.product) | `junos`  
`service` | [`meta.service.name`](../../../../docs/axoflow/reference/message-schema/reference/index.md#meta.service.name) | `eswd`, `ifinfo`, `mcsnoopd`, `mgd`, `mib2d`, `rpd`, `RT_AAMW`, `RT_FLOW`, `RT_IDP`, `RT_SECINTEL`, `RT_UTM`, `tfeb0`  
  
You can use the labels as:

  * **Filter labels** on the [Analytics page](../../../../docs/axoflow/metrics/analytics/index.md),
  * in the **Filter By Label** field during [log tapping](../../../../docs/axoflow/onboard-hosts/log-tapping/index.md).



You can use the message fields

  * in [Flow Processing steps](../../../../docs/axoflow/data-management/processing/index.md), for example, in the **Query** field of **Select Messages** steps,
  * in AQL expressions in the search bars.



## Sending data to Splunk

When sending the data collected from this source to Splunk, Axoflow uses the following sourcetype and index settings:

sourcetype | index  
---|---  
`juniper:junos:aamw:structured` | `netfw`  
`juniper:junos:firewall` | `netfw`  
`juniper:junos:firewall` | `netids`  
`juniper:junos:firewall:structured` | `netfw`  
`juniper:junos:firewall:structured` | `netids`  
`juniper:junos:idp` | `netids`  
`juniper:junos:idp:structured` | `netids`  
`juniper:legacy` | `netops`  
`juniper:junos:secintel:structured` | `netfw`  
`juniper:junos:snmp` | `netops`  
`juniper:structured` | `netops`  
  
Tested with: [Splunk Add-on for Juniper](<https://splunkbase.splunk.com/app/2847/>)

If the Axoflow classification doesn’t set the source field for the message automatically, and you haven’t set it in a [flow processing step](../../../../docs/axoflow/data-management/processing/index.md#set-fields) manually (by setting the `meta.destination.splunk.source` field), AxoRouter automatically sets the source to the [name of the AxoRouter connector](../../../../docs/axoflow/reference/message-schema/reference/index.md#meta.connector.name) that received the message (for example, `axorouter-syslog-tcp-514`).

## Sending data to Google SecOps

When sending the data collected from this source to a [_dynamic_ Google SecOps destination](../../../../docs/axoflow/destinations/google/secops/index.md), Axoflow sets the following log type: `JUNIPER_JUNOS`.

## Sending data to Microsoft Sentinel

When sending the data collected from this source to a [Microsoft Sentinel destination](../../../../docs/axoflow/destinations/microsoft/sentinel/index.md), Axoflow normalizes the data and sends it to the following table: `Syslog`.