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
Search for metrics (similar to dashboard search) #264
Comments
@bhawna2909 yes, using ES to search for Graphite metric keys is something that will eventually be added. The idea is to make be it possible to quickly search for a metric -> apply some optional function or expression template -> add add it to the dashboard or view in new/temp dashboard. Not only to make it faster for adding new graphs but make ad hoc / one time graphs more quickly. |
I don't know whether this is relevant, but Graph Explorer allows metrics to be key/value tagged, and then graphs created from queries against that kind of storage. That's really powerful; but requires writing code to dissect proto1 statsd metrics, or adopting proto2. |
remove the buffered channel between queue reader and job executors, so we have proper backpressure. see grafana#264 also assure proper error behavior in all execution related code, to ensure proper acknowledgement semantics: * panic: only for truly unrecoverable errors that require, or for which it's easiest to, stop the process * fatal errors during alert execution (e.g. bad definition, unparseable json, ...): no point in retrying later, ack the message * non-fatal, i.e. transient errors during alert execution (e.g. graphite unreachable): this is the only case we should not ack, as they should be retried later. * fix a bug where 0 email addresses specified caused final processing (store result in graphite, statsd timings and counts) to be skipped
they have different purposes, require different size settings, and different instrumentation
Can there be a global search instead, searching words in Dashboard names, Panel titles, Metric Queries, Aliases, Tags? |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Sorry, stale bot was wrongly configured (should only have acted on PRs) |
Another use case is: "Is my metric used somewhere or can I delete it?" |
This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions! |
This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions! |
It is mentioned in the grafana wiki that "Using elasticsearch for searching metrices" is still in pipeline. So it means that at present we cannot import elasticsearch indexes just like we do in kibana and use lucene based queries on it ?
The text was updated successfully, but these errors were encountered: