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

Search for metrics (similar to dashboard search) #264

Closed
bhawna2909 opened this issue Apr 1, 2014 · 8 comments
Closed

Search for metrics (similar to dashboard search) #264

bhawna2909 opened this issue Apr 1, 2014 · 8 comments
Labels
area/search stale Issue with no recent activity type/feature-request

Comments

@bhawna2909
Copy link

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 ?

@torkelo
Copy link
Member

torkelo commented Apr 1, 2014

@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.

@torkelo torkelo added the feature label Apr 2, 2014
@torkelo torkelo changed the title Using elasticsearch to search for metrices Using elasticsearch to search for metrics Apr 2, 2014
@petemounce
Copy link
Contributor

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.

@torkelo torkelo changed the title Using elasticsearch to search for metrics Search for metrics (similar to dashboard search) Jun 29, 2015
Dieterbe added a commit to Dieterbe/grafana that referenced this issue Jul 13, 2015
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
Dieterbe added a commit to Dieterbe/grafana that referenced this issue Jul 13, 2015
they have different purposes, require different size settings, and
different instrumentation
@utkarshcmu
Copy link
Collaborator

Can there be a global search instead, searching words in Dashboard names, Panel titles, Metric Queries, Aliases, Tags?

@stale
Copy link

stale bot commented Dec 2, 2019

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.

@stale stale bot added the stale Issue with no recent activity label Dec 2, 2019
@torkelo
Copy link
Member

torkelo commented Dec 2, 2019

Sorry, stale bot was wrongly configured (should only have acted on PRs)

@TWHOI
Copy link

TWHOI commented Apr 6, 2021

Another use case is: "Is my metric used somewhere or can I delete it?"

Copy link
Contributor

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!

@github-actions github-actions bot added the stale Issue with no recent activity label Jan 19, 2024
Copy link
Contributor

This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/search stale Issue with no recent activity type/feature-request
Projects
None yet
Development

No branches or pull requests

7 participants