Maniphest T105910

EPIC: expansion of data retrieved from the Cirrus search logs
Closed, ResolvedPublic10 Estimated Story Points
Actions

Assigned To

Authored By

	Ironholds
	Jul 15 2015, 4:58 PM

Project Tags

Referenced Files

None

Subscribers

Description

We keep being asked "could you get X from the cirrus logs?" "Could you get Y from the cirrus logs?"

This epic covers all the things we're being asked to get from the cirrus logs! As such it has all the stakeholder benefits of individual parts (for example, surfacing the zero results rate, one of our KPIs, in a more granular fashion) and also offers an opportunity to increase the robustness of the data collection scripts, decreasing the probability stakeholder-consumed data will be missing.

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved		Ironholds	T105910 EPIC: expansion of data retrieved from the Cirrus search logs
		Resolved		None	T102040 In the zero results stream it'd be nice to know if the user was given a search suggestion
		Resolved		None	T102042 Log whether or not the request returned a suggestion in the CirrusSearchRequests.log
		Resolved		• Manybubbles	T105360 CirrusSearch suggestions are not always logged
		Resolved		None	T102038 In the zero results stream it'd be nice to be able to filter on whether the request was a prefix search or a full text search
		Declined		• Deskana	T100715 Use the Cirrus server side logs to get some elasticsearch time took metrics

Event Timeline

Ironholds created this task.Jul 15 2015, 4:58 PM

Ironholds claimed this task.

Ironholds raised the priority of this task from to Needs Triage.

Ironholds updated the task description. (Show Details)

Ironholds added projects: Discovery-Analysis (Current work), Discovery-ARCHIVED.

Ironholds subscribed.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 15 2015, 4:58 PM

Ironholds triaged this task as High priority.Jul 15 2015, 4:59 PM

Ironholds set Security to None.

Ironholds edited a custom field.

Ironholds moved this task from Backlog to In progress on the Discovery-Analysis (Current work) board.

Ironholds added subtasks: T102040: In the zero results stream it'd be nice to know if the user was given a search suggestion, T102038: In the zero results stream it'd be nice to be able to filter on whether the request was a prefix search or a full text search, T100715: Use the Cirrus server side logs to get some elasticsearch time took metrics.

Ironholds updated the task description. (Show Details)Jul 15 2015, 5:33 PM

Aklapper added a project: Epic.Jul 15 2015, 10:57 PM

Ironholds closed subtask T100715: Use the Cirrus server side logs to get some elasticsearch time took metrics as Declined.Jul 21 2015, 9:51 PM

Ironholds reopened subtask T100715: Use the Cirrus server side logs to get some elasticsearch time took metrics as Open.

• Deskana closed subtask T100715: Use the Cirrus server side logs to get some elasticsearch time took metrics as Declined.Jul 28 2015, 7:52 PM

@Ironholds This task could use some explanation of the stakeholders and how it benefits them. Can you add that?

Ironholds updated the task description. (Show Details)Jul 28 2015, 8:00 PM

Ironholds moved this task from In progress to Done on the Discovery-Analysis (Current work) board.Jul 28 2015, 8:06 PM

Ironholds closed this task as Resolved.Jul 31 2015, 5:43 PM

Ironholds closed subtask T102040: In the zero results stream it'd be nice to know if the user was given a search suggestion as Resolved.

Ironholds closed subtask T102038: In the zero results stream it'd be nice to be able to filter on whether the request was a prefix search or a full text search as Resolved.

• Deskana moved this task from Done to Resolved on the Discovery-Analysis (Current work) board.Aug 31 2015, 6:27 PM