2 The Emitting stage: Creating and submitting telemetry

 

This chapter covers

  • Understanding what the Emitting stage does
  • Emitting telemetry from software you’re developing
  • Emitting telemetry from hardware and third-party software
  • Emitting telemetry from SaaS and IaaS platforms

The Emitting stage, shown in figure 2.1, is the first stage in your pipeline, where telemetry generated by a production system enters the pipeline. This first stage can be many things:

  • Your production code itself. A logging class inside the production code provides the needed formatting and telemetry delivery (section 2.1). You can use several techniques when emitting this way.
  • A hardware system like Cisco networking gear or Dell servers that you configure to emit telemetry (section 2.2).
  • A Software as a Service (SaaS) or Infrastructure as a Service (IaaS) platform such as Amazon Web Services (AWS), Azure, Atlassian products, or GitHub that is able to provide a telemetry stream (section 2.3).
Figure 2.1 Telemetry system pipeline stages with the Emitting stage shown first, illustrating where it fits in the overall telemetry pipeline. The Emitting stage is where telemetry enters the pipeline from the production systems. Production systems can be code, whereas the Emitting stage is often inside the production system itself, or hardware and Software-as-a-Service systems.

2.1 Emitting from production code

 
 
 

2.1.1 Emitting telemetry into a log file

 

2.1.2 Emitting telemetry into the system log

 
 

2.1.3 Emitting telemetry into standard output

 
 
 

2.1.4 Formatting telemetry for emissions

 
 
 

2.2 Emitting from hardware

 
 
 

2.2.1 Explaining SNMP

 
 

2.2.2 Ingesting telemetry from a Cisco ASA firewall

 
 

2.3 Emitting from as-a-Service systems

 
 
 
 

2.3.1 Emitting events from SaaS systems

 
 
 

2.3.2 Emitting events from IaaS systems

 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage