You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GreptimeDB currently supports only the equal matcher for metric names, such as {__name__ = 'up'}, and does not support other matchers like != or ~=.
For instance:
count by(__name__)({__name__=~"go_.*"})
I believe GreptimeDB should also support regex(and not regex) matchers, but the != matcher will not be implemented due to performance concerns.
The regex matcher will query the tables from the metric engine's internal metadata, and join the results from each metric table to return the response. Of course, we must limit the table number to return at one time to avoid OOM error.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered:
What type of enhancement is this?
API improvement
What does the enhancement do?
GreptimeDB currently supports only the equal matcher for metric names, such as
{__name__ = 'up'}
, and does not support other matchers like!=
or~=
.For instance:
I believe GreptimeDB should also support regex(and not regex) matchers, but the
!=
matcher will not be implemented due to performance concerns.The regex matcher will query the tables from the metric engine's internal metadata, and join the results from each metric table to return the response. Of course, we must limit the table number to return at one time to avoid OOM error.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: