javery
10/21/2022, 1:02 PMcole | data
10/21/2022, 3:23 PMcole | data
10/21/2022, 3:24 PMjavery
10/24/2022, 8:09 AMWorkers Subrequest
huh 😉 )toinbis
10/27/2022, 3:24 AMtoinbis
10/29/2022, 9:20 AMcole | data
11/01/2022, 9:36 PMEdgeResponseStatus
code issued for that redirect in the logs (301, 308, etc).
What you can do is head to analytics, filter by that path and see the number of status codes being 3xx.cole | data
11/01/2022, 9:37 PMcole | data
11/01/2022, 9:38 PMtoinbis
11/01/2022, 10:17 PMaddi
11/05/2022, 2:48 PMaddi
11/05/2022, 2:48 PMaddi
11/05/2022, 2:50 PMcole | data
11/05/2022, 4:02 PMFlqa
11/30/2022, 10:20 PMFlqa
11/30/2022, 10:20 PMcole | data
11/30/2022, 10:36 PMcole | data
11/30/2022, 10:37 PMFlqa
11/30/2022, 11:23 PMFlqa
11/30/2022, 11:29 PMcole | data
12/01/2022, 12:18 AMFlqa
12/01/2022, 10:12 PMcameron
01/18/2023, 10:52 AMshellspyer
03/07/2023, 11:31 PMAmandaarlene
03/10/2023, 4:18 AMalbert
04/21/2023, 11:24 AMJPL | Data PM
05/03/2023, 10:56 PMMike Eves
05/05/2023, 10:53 AMcole | data
05/05/2023, 3:20 PMMike Eves
05/09/2023, 8:39 AMcustomerId
, value: lookup_json_string(cf.hostname.metadata, "customerId")
, or alternatively a new option alongside Request/Response Header/Cookies that is 'Hostname Metadata' or similar, that just takes a key to lookup from the hostname (e.g. customerId
)
Similarly, the filters on Logpush jobs could have a similar interface.
We have some good information in our hostname metadata (application the host belongs to, the defined security policy that we target rules against etc.) so it would be really useful to have that when ingested into our Elasticsearch.
We also have some very high log volume hosts that we don't need the logs for that we could exclude if the filters supported the expression language (using a metadata field of e.g. logpush: false