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

Container log keyword filter inconsistant results #19045

Open
3 tasks done
reefland opened this issue Jul 13, 2024 · 2 comments
Open
3 tasks done

Container log keyword filter inconsistant results #19045

reefland opened this issue Jul 13, 2024 · 2 comments
Labels
bug Something isn't working component:core Syncing, diffing, cluster state cache type:bug

Comments

@reefland
Copy link

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

Using ArgoCD Container Log viewer, filtering on keywords has wildly inconsistent results. Some words work fine, other not at all.

To Reproduce

I'm reviewing Kube-VIP daemonset logs - 3 pods with fairly consistent logs, trying to find entries with specific words and it does not work as expected.

Expected behavior

I expect keyword / letter matching to work as expected.

I'm trying to search for keyword traefik, 2 letters finds a match:
image

  • I put a reference to unifi as well, I'll get to that below.

As soon as I try a 3rd character, I have no results:
image

Back the unifi example, I try to search for that, get nothing:
image

If I don't start with u and look for ni it starts to find it...
image

Enter the 3rd letter, I get nothing:
image

I try unifi on one of the other pods, works pretty well:
image

So I try traefik in that pod, again 2 letters starts to find a match, but 3 letters finds nothing as shown above.

Here are the 4 lines in the log file:

time="2024-07-13T13:04:26Z" level=info msg="Starting kube-vip.io [v0.8.1]"
time="2024-07-13T13:04:26Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[true], Services:[true]"
time="2024-07-13T13:04:26Z" level=info msg="No interface is specified for VIP in config, auto-detecting default Interface"
time="2024-07-13T13:04:26Z" level=info msg="prometheus HTTP server started"
time="2024-07-13T13:04:26Z" level=info msg="kube-vip will bind to interface [enp1s0]"

Line 2 has Mode: [ARP], try search for ARP, enter one letter finds nothing:
image

Try looking for the v0.8.1 in the version number, v finds a partial match, but v0 finds nothing:
image

Version

$ argocd version
argocd: v2.11.4+e1284e1
  BuildDate: 2024-07-02T19:17:02Z
  GitCommit: e1284e19e03c9abab2ea55314b14b1e0381c4045
  GitTreeState: clean
  GoVersion: go1.21.10
  Compiler: gc
  Platform: linux/amd64
@reefland reefland added the bug Something isn't working label Jul 13, 2024
@alexmt alexmt added component:core Syncing, diffing, cluster state cache type:bug labels Jul 13, 2024
@surajyadav1108
Copy link
Contributor

Is this specific to a particular pod, or does it occur consistently with others as well? I tried to reproduce the issue, but the filter works fine in my case.

@reefland
Copy link
Author

It's inconsistent... as another example with Grafana pods. I can easily filter on word duration:
image

I test with the numbers...
image

I try to find the 16.4 and as shown and get nothing...
image

However, the 16.1 finds matches:
image

If I try other numbers from the 1st image with arrows, nothing:
image
image


All these durations have numbers at the end of them:
image

Try to be more specific... nothing:
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component:core Syncing, diffing, cluster state cache type:bug
Projects
None yet
Development

No branches or pull requests

3 participants