Skip to content
This repository has been archived by the owner on May 28, 2024. It is now read-only.

Solr query log analysis for Argo #1099

Open
ndushay opened this issue Jan 30, 2024 · 2 comments
Open

Solr query log analysis for Argo #1099

ndushay opened this issue Jan 30, 2024 · 2 comments
Assignees

Comments

@ndushay
Copy link
Contributor

ndushay commented Jan 30, 2024

query terms - what are user entered query terms? How many are used? How many are druids? Titles? tags? etc.

facets used

...

@ndushay ndushay self-assigned this Jan 30, 2024
@ndushay
Copy link
Contributor Author

ndushay commented Jan 30, 2024

Bad news 1: we only keep 7 days of Solr logs.

Bad news 2: I grabbed the logs from the 3 sul-solr VMs containing argo prod. I then grepped for "argo" because the sul-solr VMs are used for multiple collections. I combined these logs locally. Then I grepped for path of "/select" to get the argo solr log messages pertaining to searches (as opposed to /update or /admin or ...).

I then tried to do clever greps to find the value for the Solr q params. It's certainly possible I blew it, but for 434 lines of log, I only found 89 q params and they're really not interesting.

I have attached:
file with all the argo solr requests
file with only the path "/select" argo solr requests
file with query strings

argo.solr.select.log
argo.q.terms.txt
argo.solr.log from c
argo.solr.log from d
argo.solr.log from h

@ndushay
Copy link
Contributor Author

ndushay commented Jan 31, 2024

This also implies 434 user queries in Argo for a week - that's not a lot for patterns of use. Tagging @andrewjbtw

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant