feat: save rum-traffic as metrics to s3

[rpapani]

For calculating the projected traffic lost/value, we need organic traffic from RUM for the given page. Rather than each opportunity crunching the RUM data separately, adding this rum-traffic audit, which will save the rum-traffic data to importer metrics.
So, the opportunities can obtain the rum-traffic data as

import { getStoredMetrics } from '@adobe/spacecat-shared-utils';

const rumTrafficData = await getStoredMetrics(
    { source: 'rum', metric: 'rum-traffic', siteId },
    context,
  );
const pageOrganicTraffic = rumTrafficData['<url>']?.earned || 0;

[github-actions]

This PR will trigger a minor release when merged.

[rpapani]

any preference rum-traffic vs rum-metrics ?

[dzehnder]

looks like it's only about traffic data, not other metrics. Would keep rum-traffic in that case

[ekremney]

@iuliag please review this one: possible overlap with import worker

[solaris007]

• this should be an import, not an audit. please move to import worker
• please make sure you add relevant configurations to global config / jobs dispatcher
• getStoredMetrics should not be part of utils

[iuliag]

This should be an import of type page-organic-traffic with source rum and destination default (meaning S3).

During the workshop, there were 2 discussions leading to the decision to have the metrics collection running independent of the auditing:

• ingestor service for unified metrics collection so that auto-identify and auto-suggest have all kinds of metrics available without duplicating data collection implementation and increasing COGS (see diagram in Experience Success Studio -> ingestor service tab)
• timeline for metrics collection to cover needs of the success report (whiteboarding from workshop)

[rpapani]

@iuliag

This should be an import of type page-organic-traffic with source rum and destination default (meaning S3).

sure, will move the logic to import worker

ingestor service for unified metrics collection so that auto-identify and auto-suggest have all kinds of metrics available without duplicating data collection implementation and increasing COGS

is this ingestor service available already? or the future service that we'll implement post GA? If I implement this page-organic-traffic in import worker, will this be ported to ingestor service later?

timeline for metrics collection to cover needs of the success report
I'm using 30 days as a window for collecting this data. If we make this timeline configurable, then we'll have to add that information in the metrics as well to inform the consumers about the timeline.

[iuliag]

is this ingestor service available already? or the future service that we'll implement post GA? If I implement this page-organic-traffic in import worker, will this be ported to ingestor service later?

it's not available already. we'll implement it post-GA starting from what we have in the import worker

I'm using 30 days as a window for collecting this data. If we make this timeline configurable, then we'll have to add that information in the metrics as well to inform the consumers about the timeline.

we have a time property for each metric entry https://github.com/adobe/spacecat-api-service/blob/main/docs/openapi/schemas.yaml#L1403-L1432 and you could also add either a granularity field (monthly, weekly etc.) or the time interval.