App Tracing is a powerful feature which correlates information about applications (dashboards, orchestration tools) with cluster performance data.
App Tracing can answer questions like:
- which dashboard and user is contributing to this spike in queries?
- what is the average latency of a dashboard? Of all dashboards executed by a particular user?
- my Airflow or Pinball tasks experienced a spike in latency - what caused it? Which query slowed down and why?
- my Airflow or Pinball jobs are failing, how can I quickly find those queries in Intermix?
Who Should Use this Procedure
This article is for organizations who wish to use App Tracing features, and launched an intermix.io Collector before May 2018 with scrubbing enabled.
Modifying Collector to support App Tracing
To support App Tracing, the intermix.io Collector must be aware of query tags from supported applications. See the intermix.io - App Tracing Guide for a list of supported applications.
This requires adjusting the configuration file used by the intermix.io Collector.
Follow these steps to adjust theintermix.io Collector configuration.
- SSH into the Collector instance
- Get a root shell
- Edit the file "/collector.env" to change the value of SCRUB_LEVEL to 9
- Stop the container (it will be restarted automatically within 5 minutes)
“root# docker stop intermix_collector”
That’s it. When the collector restarts, it will preserve query tags.