Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add logging to track latency for metrics as dimensions in query parsing #1223

Merged
merged 1 commit into from
May 21, 2024

Conversation

courtneyholcomb
Copy link
Contributor

Description

Logging to see if metrics as dimensions is causing major slowdowns.

Copy link
Contributor

@DevonFulcher DevonFulcher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Although, does it make more sense to use a span for this?

@courtneyholcomb
Copy link
Contributor Author

Thanks! Although, does it make more sense to use a span for this?

@DevonFulcher not exactly my area of expertise, but it's my understanding that we can't do the same type of tracing in MF that we do in MFS since it's a third party package 🤔

@courtneyholcomb courtneyholcomb merged commit 4f7dc28 into main May 21, 2024
43 checks passed
@courtneyholcomb courtneyholcomb deleted the court/linkable-metric-slow branch May 21, 2024 21:43
linkable_element_sets_for_no_metrics_queries.append(
self.get_joinable_metrics_for_semantic_model(
semantic_model, SemanticModelJoinPath(left_semantic_model_reference=semantic_model.reference)
)
)
logger.info(f"Building valid linkable metrics took: {time.time() - linkable_metrics_start_time:.2f}s")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:( we need to figure out how to add stuff to extra in MF logs.... having it as a field in DD would allow us to easily calculate all sorts of stats on it

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

Successfully merging this pull request may close these issues.

3 participants