[ARIN-consult] ACSP Consultation: Deleting Aged Report Request Tickets

[Adam Thompson]

Precisely because of the delay.  The old tickets are a way to see the info you want (albeit possibly stale) without the pause which completely messes up your workflow.

Although you raise a valid point: the problem isn't the tickets being deleted, the problem is that they are/were necessary in the first place.  With the exception of association reports which I might want for forensic purposes, I think the remainder have little historical value per se, I just want instant access to the data (and the ability to see if it had changed over time).

-Adam

On July 1, 2019 11:06:18 a.m. CDT, "Delacruz, Anthony B" <Anthony.DeLaCruz at CenturyLink.com> wrote:
>Why not just run the whowas report again and get updated info if any
>more has occurred. The same history should be in there. That probably
>is the one a do a few times a week and would be good with those all
>getting tossed out as tickets since I could just query again. I’m fine
>with the removal of the 4 listed types as the data is still accessible.
>I don’t think we need to have a record of every time the tool is use.
>Ideally just give me the info asked and don’t even make a ticket.
>
>From: ARIN-consult [mailto:arin-consult-bounces at arin.net] On Behalf Of
>Adam Thompson
>Sent: Monday, July 01, 2019 9:52 AM
>To: John Curran
>Cc: <arin-consult at arin.net>
>Subject: Re: [ARIN-consult] ACSP Consultation: Deleting Aged Report
>Request Tickets
>
>Acknowledged. I'm saying there is some value in those reports, months
>or years later. Not a *lot* of value, necessarily, but certainly
>non-zero. The casual, instant access to them is what makes them still
>useful IMHO.
>-Adam
>
>On July 1, 2019 9:25:00 a.m. CDT, John Curran <jcurran at arin.net> wrote:
>On 1 Jul 2019, at 10:11 AM, Adam Thompson
><athompso at athompso.net<mailto:athompso at athompso.net>> wrote:
>
>As an alternate suggestion, I don't see any problem with moving those
>records out of the mainline UI onto another page and into another
>database.
>
>Acknowledged.
>
>
>Like many others here, though, I'm puzzled at how a modern database
>system could be this badly hobbled (in an apparently-intractable way)
>by mere millions of tickets.
>
>The ARIN Online system handles these tickets now quite capably, but
>staff prepared the suggestion because it is clear that the system
>performance could be even better if we did not have infinite retention
>on tickets which are created solely for report generation.   Users can
>run these reports at any time to obtain such information if they desire
>it.
>
>Again, the only reason these tickets exist is that the time to go
>through the entire registry history and generate historical reports is
>significant and thus not real-time – if information had been available
>instantly, then we would have instead had it displayed directly on the
>screen and there never would have been any “report ticket" generated in
>the first place.   Given that ARIN Online creates such “report tickets”
>on the users behalf (and the questionable value of the report output
>months later), it was felt best to assign an expiration on the these
>ticket types.
>
>Thanks,
>/John
>
>John Curran
>President and CEO
>American Registry for Internet Numbers
>
>
>
>--
>Sent from my Android device with K-9 Mail. Please excuse my brevity.
>This communication is the property of CenturyLink and may contain
>confidential or privileged information. Unauthorized use of this
>communication is strictly prohibited and may be unlawful. If you have
>received this communication in error, please immediately notify the
>sender by reply e-mail and destroy all copies of the communication and
>any attachments.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20190701/e86dabcc/attachment-0001.html>