Monitor Flex Compute Usage
This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project,
feel free to reach out to us!Overview
Monitor the usage of Flex compute through various graphs on the Flex Controls page. Make informed decisions using data on cost-performance tradeoffs and balance operational success with financial efficiency.
Flex compute is limited by two factors:
- The number of concurrent queries
- The maximum number of logs that can be scanned per query
Query slowdowns occur when the concurrent query limit is reached, and a query is retrying to find an available slot to run in. If an available slot is not found, the query will not run. Datadog displays an error message advising you to retry your query at a later time.
Available metrics
The Flex Logs Controls page provides visualizations so you can assess how often query slowdowns are occurring and where they are happening most frequently. The following metrics are available:
- Query slowdowns
- Top sources of query slowdowns
- Top users experiencing slowdowns
- Top dashboards experiencing slowdowns
Optimization recommendations
Use this information to optimize your usage.
- Reach out to outlier users to:
- Discuss their querying needs
- Understand if there are logs they query frequently that should be stored in Standard Indexing instead
- Improve dashboards experiencing slowdowns by:
- Pausing the auto-refresh of dashboards
- Evaluating if logs used to power widgets can be converted into metrics to reduce the heavy Flex compute usage. For example, if dashboard widgets are only looking at a few “error” or “success” instances, but the logs themselves contain low information density, consider turning these logs into a metric
- Organizing dashboard widgets into groups, and keeping the groups collapsed until needed. Widgets in a collapsed group do not load when the dashboard is opened
- Consider upgrading your Flex compute size to increase the concurrent query limit if you notice sustained query slowdowns.
- Scope to the index you are querying. If the logs you are querying belong to a specific index, scoping to that index can speed up your search.
To learn more about compute sizes, see the Flex Logs documentation.
Further reading
Más enlaces, artículos y documentación útiles: