Skip to content
This repository has been archived by the owner on Apr 27, 2022. It is now read-only.

consider using spark.metrics.namespace #79

Open
erikerlandson opened this issue Sep 22, 2017 · 2 comments
Open

consider using spark.metrics.namespace #79

erikerlandson opened this issue Sep 22, 2017 · 2 comments
Labels

Comments

@erikerlandson
Copy link

This is an issue to brainstorm about possible uses of spark.metrics.namespace, as described here

A possible example. Set spark.metrics.namespace to the spark cluster name assigned by the user or oshinko. So for a cluster named "wilma" the metrics from driver and executors would be:

wilma.metric.name instead of spark_app_uid.metric.name

@elmiko
Copy link
Contributor

elmiko commented Nov 3, 2017

i feel like this is something that app developers should be doing in their code. it might be nice to have a default back to the cluster name, but i'm not sure how we would avoid stomping on the value provided by an app in that case.

@elmiko elmiko added the question label Nov 3, 2017
@tbradellis
Copy link

So, would this be:
spark.metrics.namespace.${spark.app.name}

or
spark.metrics.${spark.app.name}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants