Hi Mikhail,

Thank you for your work on this. I have some comments:

- There is already a short link (https://s.apache.org/beam-community-metrics).
Would a link from contributing to beam page (if there is not one already)
sufficient> People can bookmark the short link if they need to quickly
access.
- Metrics is a developer facing tool. If it has its own subdomain and start
showing up in web search results, it will be a confusing landing page for
people simply searching for "beam metrics". I believe there is some value
in having a single domain and linking to various things from there. This
would be similar to how we link to jira, wiki, mailing list archives.

Ahmet

On Fri, May 17, 2019 at 9:26 PM Mikhail Gryzykhin <
gryzykhin.mikh...@gmail.com> wrote:

> @Aizamat
> Code is not generalized and is project specific in some places. But it is
> small and pretty straightforward so can be ported easily. Whole thing can
> be started locally with a single docker command, so it's easy to try it out.
>
> On Fri, May 17, 2019, 19:33 Aizhamal Nurmamat kyzy <aizha...@google.com>
> wrote:
>
>> Hi Mikhail,
>>
>> I think this dashboard is amazing, and would love to have an easy access
>> to it. So here is my non binding +1.
>>
>> On the side note, how easy is to recreate it for other Apache projects? ;)
>>
>> Thanks,
>> Aizhamal
>>
>> *From: *Mikhail Gryzykhin <mig...@google.com>
>> *Date: *Fri, May 17, 2019 at 6:49 PM
>> *To: *dev
>>
>> Hello everyone,
>>>
>>> Some time ago we started community metrics dashboard.
>>> <https://s.apache.org/beam-community-metrics> However we never had
>>> added a permanent URL for it. This is really inconvenient to use, since
>>> only available way to access dashboard is by IP-address.
>>>
>>> In this tread I'd like to:
>>> 1. Vote to assign metrics.beam.apache.org to metrics dashboard (
>>> http://104.154.241.245).
>>> 2. Gather information on how to do it. I can assume only following steps
>>> so far: a) vote b) once vote is complete, contact Apache INFRA to help with
>>> this.
>>>
>>> Regards,
>>> Mikhail.
>>>
>>>

Reply via email to