Thanks to all who joined us and submitted questions to the Cisco IOS XR & SignalFx demo Q&A session. During the DemoFriday, we learned all about the new release of IOS XR 6.0.0 and Streaming Telemetry, how you can monitor your network needs to evolve with the modern networks and applications, and how to make dynamic alerts a priority. After the live demonstration from both Cisco and SignalFx, there was a thoroughly engaging Q&A session. Unfortunately, SDxCentral ran out of time to be able to ask all the questions the audience asked. Read the full Q&A below:
Can the telemetry policy be dynamically applied?
Cisco: Yes, we will be able to dynamically apply policy in a pub-sub mechanism.
What other encodings/transport can be supported?
Can you filter the data that is streamed from the box?
Cisco: Yes, you can filter down to the model or leaf level.
Can I use SignalFx to monitor SNMP?
SignalFx: Yes, SignalFx can leverage the SNMP plugin for Collectd to collect metrics. However, the richness of the data will be limited to SNMP and the frequency will be limited to the SNMP limits.
If my JSON object is sending hundreds of measurements per second, do you store each measurement or an aggregate of it per min?
SignalFx: SignalFx is capable of receiving data points for a single time-series more frequently than one per second. In the case that this happens we will perform an aggregation of all of the points received in a given one second interval and store only the aggregate value. For more on our default roll-up policy you can find them here.
How does SignalFx handle missing or dropped data points?
SignalFx: SignalFx allows the user to define how they would like to handle missing to dropped data points at the per-time series level. This allow you to define different policies based on data type that is being submitted. Read about the various options here.
Can I filter the data points that are sent to SignalFx?
SignalFx: SignalFx allows you to have full control of the metrics and datapoints that you send to the service. You can either configure this in the collector that you are using (i.e. logstash, collectd, etc.) or by using the SignalFx Metric Proxy. The Metric Proxy is designed for users that are sending data to SignalFx from a private or on-prem environment. You can learn more about the Metric Proxy here.
Is SignalFx only over IOS XR v4 initially?
Cisco: It’s address-family agnostic. You can do v4 and v6.
Will Streaming Telemetry require a separate license on upcoming IOS-XR release 6.0.0?
Cisco: I would recommend consulting your account team for licensing details.
Which push model(s) are being used for streaming, e.g. IETF, OC…etc?
Are the transport protocols based on NETCONF or we are looking at something like gRPC?
You mentioned pre-calculating data as its collected, making it more efficient to render historical graphs. How long do you keep the unaggregated data?
SignalFx: We store the data points you send at their native resolution for eight days. After eights days, we roll it up to coarser resolutions and retain it for a year. If you’d like to retain the data at higher resolution or for longer, get in touch – we’re more happy to discuss options.
Is streaming central (CPM) or of line cards?
Cisco: It really depends on the data. Some is necessarily central (e.g. link bundle stats) but some can come straight from the LC.
How does that fit with NETCONF notifications?
Cisco: It is complementary. If you want the data in XML over SSH, we can do that. It’s all the same underlying data.
When is the IOS-XR Release 6.0.0 with Basic Streaming Telemetry support, somewhere around in Q2, 2016?
Cisco: Streaming telemetry shipped in XR 6.0.0 on the NCS 5500 series platforms. Other platforms will follow soon.