►
From YouTube: CDF SIG Events - August 23, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
B
C
A
I
think
some
was
canceled,
I
was
on
vacation
and
some
was
canceled
during
my
absence
and
last
time
two
weeks
ago
we
just
accept
me
and
Steve
Pereira
from
bsmi.
It's
very
short
sync.
Yes,
then
so
not
too
frequent
or
not
to
well
attended.
I
would
say.
C
A
D
Yeah,
initially,
that's
why
I
thought
like
work
group
meeting
is
the
right
one,
because,
like
I
see
there,
there
are
different
delays
like
from
different
companies.
A
A
But
we
have
Victor
Villas
at
night
at
least
now,
that's
great
so
I
guess
we
could
anyway
have
a
presentation
of
what
you've
done
the
Lander
and
then,
if
needed,
we
could
maybe
come
back
to
it.
There
is
a
meeting
next
Tuesday
as
well,
and
then
Andrea
is
back
as
well.
Maybe
we
can
repeat
part
of
it
at
least
then,
if
that's
okay
with
you.
D
A
Yeah
or
let's
have
it
now
then,
and
the
recording
will
be
posted
on
YouTube
and
then
we
can
refer
to
that
one
and
urge
everyone
to
to
look
into
it
if
they
haven't
seen
it
like
so
I
think
we
get
started
before
we
get
into
the
representation
or
the
discussion
about
his
Association
I
can
just
share
some
some
quick
intro
so
get
the
link
to
the
meeting
minutes
on
here.
Please
sign
up.
A
And
yeah
just
a
very
short
agenda
before
we
get
into
the
demo
no
action
items
from
previous
meetings
as
I
recall
after
some
other
CDF
groups,
I
just
added
an
update
of
the
CD
events
group,
there
I
haven't
attempted
any
other
CDF
groups
recently
I'm,
not
sure
if
they
have
been
very
active
over
the
summer,
but
one
thing
that
might
be
a
bit
interesting.
It
is
that
we
now
have
a
interested
party
working
on
a.net
SDK
for
City
events,
the
focus
there
is
durometrics
I
believe
it
was,
and
the
guy
who
will
contribute.
A
This
will
come
to
us
in
a
month
or
so
to
talk
more
about
it.
Let's
just
heads
up
over
the
usdk
coming
and
then
about
the
conferences.
I
guess
most
of
you
already
know
that
there
is
a
open
source
Summit
in
in
Spain
in
a
few
weeks,
and
it
will
also
be
possible
to
attend
virtually
there
now.
The
City
Minnesota
previously
was
announced
to
be
just
physical,
but
I
saw
now
that
it's
possible
to
return
virtually
that's
great
I
won't
be
able
to
be
there
in
person,
so
I
will
join
virtually
instead.
A
A
D
Yeah
welcome
to
this
presentation
today,
so
we'll
be
presenting
visually
visualization
using
CD
event.
So
earlier
we
have
in
existing
box
that
you're
aware,
like
there's
a
CD
events
POC,
so
that
will
interact
with
different
tools
like
pectin,
Captain
Spinnaker,
and
so
we
are
building
a
visualization
POC.
On
top
of
that
to
show
how
different
events
are
like
communicating
with
each
other
and
what
happens
in
the
sequence
of
next
even
occurs
so
I
have
a
team,
Adam
and
Andrew
working
together.
D
We
are
working
together
on
this
POC,
so
yeah
we
have
a
simple
agenda
so
wherein
like
we
will
show
visualization
using
CD
events
and
the
demo
how
we
visualize
CD
events
in
using
an
existing
City
events.
D
So
we
have
so
to
discuss
like
why
we
want
to
visualize
CD
events
in
the
first
part.
So
so
we
know
like
using
CD
event,
so
we
are
achieving
the
bigger
concept
of
what
is
interoperability.
So
apart
from
interoperability,
so
CD
events
can
also
use
to
to
to
visualize
the
stuff
like
troubleshooting
and
tracking,
storing,
and
you
can
analyze
and
visualize
the
events
across
different
clcd
tools
within
the
cacd
ecosystem.
D
So
for
that
purpose,
so
we
are
like
doing
some
investigations
on
visualization
concept
like
how
we
can
build
visualizing
events
by
using
different
clcd
components.
So
our
team
developed
a
POC
to
experience
an
end-to-end
cacd
workflow
using
this
CD
events,
so
from
a
change
committed
until
the
deployment
phase
and
different
product.
What
products
are
involved
in
this
and
how
the
events
are
triggered
in
a
sequence.
D
So
to
do
that,
so
we
have
initially
investigated
two
different
types
of
visualizations
that
is
CD
events,
aware
tool
so
which
is
actually
I,
feel
busy
based.
So
it
knows
like
what
exactly
the
CD
event
in
a
format
as
is
and
and
display
or
visualize
the
events
in
a
live
format
and
another
tool
that
we
have
explored
is
a
generic
Tool
using
a
graphana.
So
this
actually,
we
will
be
converting
a
CD
even
to
graphene,
understandable
event
in
format
and
store
it
in
a
DB.
D
So
that's
the
graph
database
that
we
have
used
for
this
purpose
and
it
will
visualize
the
events
in
the
the
dashboards.
What
grafana
is
having
so
it's
different
panels
so
to
have
this
visualization
linking
so
we
have.
We
have
created
a
links
within
the
events
taking
the
previous
events
IDs
and
then
as
a
Target,
to
show
the
relation
between
different
events.
So
the
links
are
assumed
here,
like
it's
not
coming
as
such
from
the
CD
events,
because
they
don't
exist
now.
D
So
it's
still
in
discretion,
phase
that
we
have
need
to
include
the
links,
but
here
we
just
created
After,
we
receive
the
event,
so
we
are
constructing
links
within
that.
The
time
with
me
tariffs,
so
the
example
clcd
workflow
from
commit
to
deployment
like
if
you
see
in
general,
so
in
any
GitHub
like
we
will
have
a
change
committed.
So
it's
built
by
some
tool,
it's
called
restectin
and
is
deployed
in
staging
using
Flex,
CD
and
so
Jenkins
run
some
ex
run.
D
Some
tests
on
the
deployed
staging
application
and
Captain
do
some
quality
checks
and
Spinnaker
deploys
in
production.
So
this
is
the
General
cacd
workflow.
That
shows
how
it
looks
from
computer
deployment,
so
how
we
can
visualize
this
in
these
different
tools
that
we
can
show
in
the
demo.
So
to
do
that
purpose.
Actually,
so
we
are
also
integrating
GitHub
actions,
also
with
the
CD.
Even
Spock
to
show
how
exactly
the
visualization
works
from
commit
to
deployment.
So
to
start
with,
so
we
have,
we
have
introduced
GitHub
Integrations
with
the
city
and
Spock.
D
So
we
have,
you
know
like
we
have
already
existing
CD
events,
data
actions
so
that
produces
CD
event,
so
we
reuse
the
same,
and
the
workflow
workflow
is
created
to
send
a
CD
event
from
Source
repository
where
we
wanted
to
do
some
Source
commit
I,
mean
change,
update
the
source
or
something
so
so
that
that
Source
repository
will
have
a
workflow
created
to
send
the
CD
event
by
using
CD
event
setup
actions.
D
So
another
thing
we
wanted
to
highlight
is
like
we
are
running
on
self-hosted
Runners
here
so
to
reach
the
local
Cloud
events
broker.
So
because
this
actions
runs
on
the
public
network,
so
we
are
not
able
to
reach
the
events
broker
so
that
sits
in
within
our
Network.
So
we
are
like
trying
to
run
a
self-hosted
Runners
with
setup
actions,
so
that
link
is
here
like
it
shows
how
to
configure
the
self-hosted
runners
so
that
actually
the
workflow
looks
like
what
is
on
the
left
side.
D
So
the
workflow
created
to
send
the
CD
event
and
which
uses
so
this
is
I
poked.
The
uses,
jitterb
action
is
like
I
hope
to
my
private
repository
to
make
some
changes
on
top
of
what
exists
now,
because
I
need
to
send
a
a
type
of
CD
event
so
which
which
looks
actually
the
curl
command
exactly
this
to
a
specific
events
broker,
which
is
running
within
our
private
Network.
So
this
this
is
the
configuration
like
to
send
SED
events
from
date
of
actions
that
we
have
used.
D
So
this
is
the
integration
with
the
CD,
even
Spock,
that
we
have
done
so
to
start
with
the
existing
box.
So
we
have.
We
know
that
we
have
an
existing
POC
so
which
actually
emits
the
cloud
CD
events
from
different
components
like
tecton,
Captain,
Spinnaker
and-
and
so
this
this
is
the
existing
CD,
even
Spock,
so
that
is
available
now.
So
we
introduced
a
GitHub
actions
to
this,
so
that
sends
a
CD
event
to
the
same
Cloud
events
broker,
and
so
we
can
so
with
this.
D
So
we
can
visualize
the
change
being
committed
from
a
commit
to
deployment
with
different
tools.
So
this
techton
Captain
Spinnaker
things
is
already
existing,
and
so
we
want,
we
are
building
integrating
agitive
actions
with
this
and
all
all
these
events
will
be
visualized
by
using
a
CD
events
visualizer.
So
this
is
the
new
component
that
have
have
created,
so
it's
actually
a
project
that
we
have
created
and
the
POC
has
a
different
components
in
it.
D
So
we
have
like
a
monitor,
CD
events
component,
so
that
looks
for
all
the
events
that
is
happening
within
the
cloud
events
broker
and
that
receives
every
event
that
is
coming
over
this
Cloud
events
broker
and
did
cache
the
events
fry
for
displaying
CD
events
in
different
tools.
So
we
are
also
storing
this
events
for
the
promotions
or
grafana
dashboard
purpose
and
the
same
events
will
be
used
for
seed
events,
aware
tools.
So
this
is
the
types
of
CD
events
that
we
have
implemented.
D
The
display
CD
events
implements
different
types
of
CD
events
that
they
can
Implement.
So
we
have
three
different
types
of
implementation.
That
is
right
currently,
which
is
CD
events
aware
tool
and
the
promotes
and
the
grafana
dashboard
and
the
implementation
for
the
database
store.
D
So
these
different
implementation
implementations
that
is
exist
in
the
CD
event
visualizer
currently,
so
we
can
see
like
how
different
tools
gets
the
event
and
that
visualize
at
the
same
time
by
using
so
it
even
server
tool
and
the
promote
your
server
dashboards
so
that
that
will
be
showing
in
a
demo
so
actual
the
demo
use
case
is
the
same
as
what
we
have
with
the
CD
wins
POC.
D
Apart
from
this,
the
change
using
GitHub
GitHub
action,
so
we
are
using
a
change
committed
action,
so
that
is
the
additional
integration
for
this
demo.
So
the
initially
the
change
will
be
committed.
D
So
jitterb
action
sends
an
event:
change,
merge,
CD
event,
so
that
will
be
received
by
Tekken
and
tecton
starts,
building
a
new
version
of
container
image
from
the
repository
where
it
comes
in
it
downloads,
the
the
source
code,
from
the
repository
where
the
change
first
event
came
from
and
builds
and
container
a
new
version
of
container
image,
and
once
the
container
image
is
successful,
it
sends
an
artifact
packaged
event.
D
So
this
essentially
all
the
events
are
going
to
the
cloud
events
broker
and
that
Cloud
events
broker
like
subscriptions.
These
different
components
are
subscribed
to
listen
to
these
different
types
of
events,
so
that'll
I'll
show
when
it
comes
in
the
demo,
how
it
actually
looks
the
subscriptions
and
triggers
and
the
artist
when
texting,
produces
the
artifact
packaged
event.
D
So
Captain
is
actually
subscribed
to
listen
to
that
type
of
event,
so
once
it
receives
so
Captain
have
a
manual
sequence
that
is
running
so
it
can
approve
or
deny
the
artifact
that
is
published
or
packaged.
D
Sorry
and
Captain
can
send
artifact
published
event,
so
once
it
is
approved,
so
it
will
send
an
artifact
published,
even
so
that
is
subscribed
by
Spinnaker
back
in
So,
Spinnaker
receives
an
event
and
Spinnaker
runs
the
deploy
a
pipeline
So
within
Spinnaker,
taking
the
inputs
from
what
is
artifact
published
and
it
it
just
builds
the
it
deploys,
the
artifact
that
has
come
and
since
finally,
the
service
deployed
even
so
the
same,
it
is
received
by
captain
to
Mark
the
sequence
as
successful
within
Captain.
D
Yeah
so
I'll
I'll
show
this
demo
use
case
and
all
these
CD
events
that
we
can
visualize
in
different
tools
that
I
I
talked
about
like
in
seed
events,
aware
tool
the
disciple
based
and
in
the
craft
center
dashboard.
So
I
will
show
how
this
demo
works
exactly
so,
yes
to
start
with
so
I
have
this
givench
repository
so
where
I
will
make
the
change
and
commit
to
this
repository,
and
let's
see
the
first
use
case,
maybe
yeah
so
I
I
will
do
some
changes
on
the
the
POC
Docker
file.
D
Let's
see
in
index.html
to
a
small
change,
SLB
change,
it's
nothing,
but
just
to
make
this
commit
changes.
Enable
I
will
just
commit
the
change
and
I
have
actions
running
here,
because
I
have
created
a
workflow
to
trigger
this
action
on
committing
to
the
master
that
I've
showed
in
a
slide.
D
So
now
this
runs
a
yeah,
so
this
workflow
runs
an
action
so
that
to
send
a
CD
event
so
which
actually
actually
send
a
CD
event
to
the
Cloud
events
broker
yeah,
so
it
it
runs
and
sends
a
CD
event
here.
So
you
can
see
the
post
that
is
accepted
by
Cloud
events
broker
yeah.
So
now
this
goes
green
yeah.
So
the
action
is
done.
D
So
we
could
see
the
change
merged
event
is
sent,
so
we
can
see
the
event
is
actually
sent
from
GitHub
and
that
will
be
that
that
is
actually
subscribed
to
by
techton
to
listen.
So
one
stackton
receives
an
event,
so
tecton
starts
building
an
artifact
using
that
source
code.
So
let's
refresh
this
tecton
dashboard,
so
we
could
see
a
pipeline
is
running
here
yeah.
So
this
is
the
pipeline
that
we
started.
So
this
is
because
of
network
error.
D
Mini
refresh,
so
the
change
merged
event
is
actually
triggered,
so
that
is
also
received
by
the
visualization
tools
that
I've
talked
about.
Like
you
see
the
CD
events
dashboard,
so
you
can
drift.
This
is
the
the
grafana
dashboard,
so
we
have
actually
created
a
CD
events
dashboard
so
that
have
two
different
three
different
panels
to
show
see
the
event
sequence
and
the
graph
and
and
the
logs,
actually
so,
by
using
a
different
plugins.
D
So
this
dashboard
is
created
to
show
what
what
are
the
learning
running
logs
in
the
CD
wins
visualizer.
Actually,
so
we
can
see
in
the
last.
So
this
is
the
recent
log
we
can.
We
could
see
that
source
pipeline
run
started.
This
is
the
event
that
is
arrived
actually
so,
and
the
change
merged
events
before
this
hit
code.
So
now
we
could
see
the
change
merged
event
has
come
and
then
this
make
the
pipeline
run
started
within
the
tecton.
So
we
could
see
this
is.
D
D
Yeah,
so
it
cloned
and
then
so
the
basically
the
pipeline
is
running
to
build
the
artifact
so
that
we
can
see
here
and
also
so.
We
could
see
the
this
panel
we
can
use
like
if
you
input
the
CD
event
ID.
So
you
can
see
the
representation
of
nodes
here
with
the
different
types
of
events
that
is
flowing
within
the
cloud
events
broker.
So
that
comes
with
the
CD
events
ID.
So
with
this
ID,
so
the
link
starts
building
up
within
the
servers
all
right.
D
So
if
you
query
with
this
ID,
so
we
could
we
could
get
three
different
nodes,
so
the
first
one
like
we
have
got
CD
change,
merge.
That
is
the
source
from
our
Channel
events.
So
this
is
the
source
that
we
have
got
this
CD
change
first
event,
and
then
we
have
got
another
event
here,
so
that
is
a
pipeline
run
queued.
So
this
is
triggered
by
techton
and
we
could
see
the
pipeline
run
started
also
at
the
same
time.
So
we
have
got
this
from
technina
as
well,
so
yeah.
D
D
D
Yeah,
so
it's
actually
building
the
image
and
trying
to
push
to
the
local
kind
registry.
So
that's
where
the
Spinnaker
will
use
for
the
deployment.
D
D
So
here
also,
we
can
see
like
how
different
nodes
are
flowing
in
with
the
cloud
events
broker,
so
that
we
can
see
what
events
are
coming
like
how
the
flow
is
yeah.
So
we
get.
We
have
created
a
a
repository
here
to
listen
to
it's
a
CD
events.
Live
events
live
data,
so
here
we
could
see.
So
this
is
the
previous
run,
so
that
has
it's
a
sequence
one.
D
So
now
the
another
sequence
that
you
could
see
is
the
CD
change
most
and
the
pipeline
that
started.
So
these
two
events
are
there
like
with
the
with
this
tool.
Currently,
so
we
can
refresh
when
the
different
event
comes,
and
we
can
see
like
what
events
are
sent
by
different
components
and
then
what
is
the
state
of
current
one?
D
So
it's
it's
still
going
on
this
image.
Build
takes
a
little
bit
time
but
yeah
so
once
the
tecton
build
like,
as
for
you,
as
per
the
use
case,
Captain
registered
to
this
event
like
what
tecton
bills
and
sends
an
artifact
packaged,
even
so
that
is
actually
registered
by
Captain
I
mean
subscribe,
detecting
yeah,
so
I
think
looks
like
this
is
done
so
we
have,
we
could
see
the
new
event
type
has
arrived,
but
detector
still
shows
it
is
not
green
right.
D
Oh
yeah,
so
we
could
see
this.
This
build
is
completed
right.
So
this
it
push
the
images
from
the
repository
where
it
could
build
so
yeah.
We
can
see
the
Bill
and
push
logs
basically.
D
It
actually
sorry
yeah,
so
this
is
the
one
I
want
to
show.
So
the
image
digest
what
we
can
look
for
is
so
this
is
the
latest
Bill
latest
image
that
it
has
decton
build,
and
this
once
it
is
built,
so
it
will
send
an
event
like
artifact
packaged
even
with
the
image
details
and
Captain
receives
the
event
with
these
details,
so
we
can
see
the
image
is
matching
with
what
it
is
built.
Eight
zero
one
of
ending
with
it's
eight
zero
one.
D
If
and
once
you
approve
this,
so
Captain
sends
an
event
like
artifact
published
event,
so
that
we
can
see
even
in
the
dashboards
so
now
so
because
the
pipeline
run
is
finished,
so
we
can
see
the
pipeline
run,
finished,
nodes,
updating
and
the
logs
updating
about
the
pipeline
unfinished
event
before
we
just
start
going
for
artifact
package.
So
we
could
see
here.
D
The
artifact
is
packaged
from
the
source
is
stacked.
In
the
same
time
like
we
can
see
from
see
the
events
visualization
tool
as
well,
which
is
the
CD
event,
server
tool,
the
two
types
of
different
two
different
types
of
tool
that
I've
talked
about
in
the
presentation.
So
one
is
the
CD
events
aware
tool
and
the
dashboard,
the
graphene
dashboard
so
yeah.
It.
D
Yeah,
so
now
we
could
see,
the
pipeline
run
is
finished
in
this
sequence.
Three,
the
pipeline
run
is
finished
so
and
the
same
nodes
comes
here
with
pipelines
and
finished,
so
we
can
also
see
the
details
of
like
here,
so
we
have
click
on
that
particular
node.
So
we
can
see
like
how
many
times
the
pipeline
run
finished.
Events
come
across
and
about
this,
the
time
of
it.
What's
the
different
sources
of
it,
so
similar
information,
what
we
can
find
in
the
graphene
dashboard,
so
it
will
be
available
here
with
different
sequences.
D
So
this
is
the
aggregation
that
we
have
is
chosen
either.
It
shows
the
relation
between
the
events,
and
here
we
could
see
the
the
logs
and
and
the
nodes
that
it
will
show
the
events
when
it
comes
in.
So
we
can
also
see
this
this
panel.
It
is
looking
ideal,
so
we
can
see
something
here
from
this,
so
we
can
run
some
queries
from
the
data
that
is
already
available
to
see
different
kind
of
metrics.
D
So
here
so
there
are
some
metrics
created
by
default
with
different
types
of
event
types.
D
So
we
can
see
something
like
a
a
matrix
related
to
artifact
packaged
created
by
not
effect
packaged
in
total
and
how
many
are
published
and
how
many
services
are
deployed,
so
different
metrics
can
be
configured
and
that
can
be
visualized
in
a
in
a
graph
format,
graph
and
tablet
format.
So
to
start
with,
so
we
can
select
anything
like
how
many
of
artifact
published
V1
in
total.
So
if
I
just
want
to
run
this
and-
and
we
can
add
different
queries
all
together
here,
so
this
is
much
much
more.
D
We
can
do
like
if
we
have
a
a
knowledge
on
like
how
to
use
the
grafana
dashboard
more
in.
So
we
have
tried
a
minimum
things
with
this.
What
what
we
have
knowledge
on
so
but
yeah,
so
many
things
can
be
done.
I
guess
we're
using
these
existing
metrics
and
then
queries.
So
we
can
write
custom
queries
and
then
make
any
filters,
so
that
is
available
so,
but
for
now,
like
I
will
show
many
the
basic
things
like
what
I
can
find
here.
D
So
to
attach
this
so
I
can
yeah
run
two
different
things
like
I
can
compare
so
how
many
artifacts
were
placed
and
how
many
service
deployed
in
the
last
six
hours
that
I've
selected
for
so
I
can
apply
these
to
show
in
my
current
dashboard.
So
that
will
be
exist
for
this,
at
least
when
I
rerun.
D
So
when
the
events
come
so
I
can
I
can
refresh
this
panel,
so
I
will
get
to
how
many
events
are
increased,
so
I
should
see
one
increment
in
the
order
had
published
and
one
increase
in
the
service
deployed
even
so
right
now
it
is
33,
so
maybe
you
can
see
end
of
service
deployed,
so
they
should
rest
before
yeah.
So
the
next
part
of
use
case
like
we
should
accept
this.
D
D
Whatever
yeah,
so
it's
it's
going
on,
so
the
reply
is
in
progress.
So
the
same
time
we
can
see
the
Spinnaker
is
received
this
event
and
and
it
deploys
the
artifact
so
yeah
so
running.
The
use
case
with
this
tools
is
all
existing.
D
So
right
now
we
have
in
the
C
Givens
POC
repo,
so
but
what
we
have
we
are
trying
to
show
is
like
visualization
is
the
main
concept
in
with
this
presentation,
how
you
can
visualize
these
live
running
events
with
different
types
of
CD
events,
Tool
that
we
have
explored
on
so
now.
We
could
see
these
Services
deployed
actually
so,
and
this
sends
a
service
deployed
even
to
the
captain
back
as
per
use
case,
and
this
is
how
it
marks
the
deploy
is
successful
and
we
could
see
the
service
deployed
is
Success.
D
D
Yeah
here
the
node
is
updated
with
this
yeah,
so
the
service
deployed.
So
this
is
the
IP
of
my
Spinnaker
running
so
the
Spinnaker
source
and
the
artifact
published
is
actually
from
the
captain
so
that
I
can
see
here
and
that
fat
packaged.
So
this
is
the
previous
one
so
that
I
have
got
two
editions
of
nodes
with
two
different
nodes
that
I
can
see
here.
D
So
at
the
same
time,
so
I
can
see
the
logs
as
well
so
the
running
logs
that
I
have
just
received
on
this
event,
so
that
is
the
service
deployed
and
the
artifact
were
placed
from
Source
captain
and
from
Source
Spinnaker.
D
So
yeah,
let's
refresh
even
this,
so
This,
should
get
update
with
the
pipe
blender
finished
after
pipeline
refinished.
It
should
append,
with
the
different
events
that
it
received
the
cloud
events
will
received.
D
D
So
yeah,
so
here
we
could
see
the
events
arise
is
earlier.
It
was
33
and
34..
So
this
is
the
with
the
data
available
that
we
can
show
the
graph
of
different,
so
we
can
match
with
different
types
of
events
and
what
is
the
total
total
of
events
or
different
types
of
events
created?
So
these
are
the
counters
that
is
created
whenever
the
events
has
created.
D
So
we
can
think
of
like
different
counters
that
we
can
add
when
we
are
receiving
an
event
so,
but
we
have
created
a
basic
metrics
counters
for
this
metrics
to
display.
So
that's
that's
more
about
the
CD
events
like
graphene
dashboards,
this
two
three
dashboards
that
we
have
explored
on
and
yeah
I
feel
visualization
part.
So
we
have
yeah
in
the
sequence
three.
So
this
is
service
deployed
and
my
God.
This
looks
something
different
foreign.
D
Service
deployed,
so
this
I
could
see
some
another
pipeline
run
keyword.
Maybe
it's
misplaced
from
there,
so
in
some
bug
inside
so
I
have
got.
Some
extra
even
looks
like
what
I'm
not
supposed
to
get
this
here.
Likewise
I'm
getting
in
dashboard,
proper
grafana
Let
me
refresh.
This
even
I
have
got
here.
D
Yeah,
so
that's
about
all
different
use
case
that
we
can
see
the
visualization
and
yeah.
So
this
is
the
like:
the
demo
you've
seen
with
CD
and
software
tool,
so
what
it
comes
with
CD
change,
most
and
Pipeline,
and
queued
Pipeline
and
started
finished
and
packaged
so
all
the
nodes
that
we
can
see
with
the
aggregation
and
the
details
of
each
node.
We
can
see
like
the
different
times
and
source.
D
This
is
about
the
CD,
even
software
tool
using
Ifill
based,
but
this
one
is
like
using
the
grafana
dashboard,
a
generic
tool
yeah,
so
that
we've
seen
the
different
nodes
and
graph
and
logs
yeah
so
yeah.
So
all
the
references
are
added
here
for
the
repositories
and
recordings
existing
demos.
A
E
E
Yes,
how
long
did
it
take
for
you
to
pull
all
this
all
these
pieces
together?
How
long
have
you
been
working
on
this.
D
Oh,
it's
been
like,
so
we
are
working
on
for
the
past
three
months.
Yeah,
it's
it'll
be
like
three
months
now.
E
D
E
There
a
way
do
you
think
that
we
as
this
progresses
forward,
that
we
could
we
can't
use
terraform
anymore,
but
there's
a
way
to
you,
know,
put
a
put
it
all
together
to
share
it.
I
know
that
there's
been
discussion
about
you
know,
making
our
on-ramp
as
easy
as
possible
and
you're
using
open
source
tools,
so
it
seems
like
we
could
create
one
big
container
that
has
everything
in
there
that
people
would
need
to
play
on
it.
D
Yeah
sure
so
we
have
already
a
repository
that
is
created
within
CD
events,
so
it's
City
events
visualization.
F
D
There
we
are
like
we
have
some
stuff
there
already
pushed
so
we'll
publish
soon
like
with
the
with
the
main
branch
so
that
we
have
like
currently
in
all
private
branches.
The
changes
are
lying
into
relatively
yeah
publicly.
E
Great
and
then
the
last
question
I
would
have,
if
you
want
to
do
this
for
a
you,
want
to
do
this
demo
or
CDA
CDF
Meetup
in
October
or
November.
D
E
Well,
if
that
is
of
interest
to
the
team
and
if
you're
willing
to
do
it,
we
could
get
it
on
the
calendar
for
I
would
say
sometime
in
late
October,
early
early
November.
A
A
D
D
Yes,
actually
so
it's
kind
of
mimicked
what
we
play
around
with
the
links
right
now.
So
it's
only
the
time
based
like
when
the
event
comes
first,
so
it
will
be
linked
with
the
the
next
event.
D
Yeah
so
that
some
additional
event
came
so
maybe
like
I,
see
some
issue
with
the
artifact
I
mean
like
tecton,
so
it
runs
in
a
loop
like
to
send
some
events.
I
mean
like
artifact
packaged
event.
It
sends
multiple
times,
even
if
we
like,
if
even
if
it
receives
the
CD,
changed
much
event
once
so
I'm.
Actually
so
it
I
face
this
issue,
sometimes,
but
not
every
time.
So
I
need
to
look
at
that
like
why
deckton
continuously
sends
different
types
of
events.
A
It
would,
of
course,
be
even
better.
We
had
the
real
or
the
thought,
the
linking
of
events
in
place
before
we
before
we
modest,
spread
this
wider
and
make
it
a
box
that
others
can
build
on
top
of
as
well.
But
as
you
know,
yes,
that's
the
connecting
events
be
or
still
have,
some
time
before
it
will
be
be
there.
A
We
are
working
on
the
molested
discussion
around
it.
I
would
say
not
the
actual
changes
in
the
course
so
far,
so
it
will
take
some
more
weeks
behold
before,
rather
so,
if
we
should
have
it
presented
on
a
CDF
Meetup
in
October
I
doubt
we
can
have
that
in
place
by
then
potentially
for
November,
but
I'm,
not
sure.
Let's
see
yes,.
E
A
E
A
Yeah,
it's
it's
good
to
see
that
things
are
progressing
and
that
we
can
actually
both
connect
things.
I
mean
now
we'll
get
the
vaccines
in
place
as
well
for
this
in
in
the
loop
and
then
also
visualize.
How
things
happen
I'm,
not
sure
if
we
could
also
maybe
reflect
a
bit
on
the
Dora
metrics.
Based
on
this,
we
have
some
some
metrics
for
change
to
deployment.
A
A
E
A
A
F
Yeah
I
was
just
curious.
I
probably
didn't
look
in
this
in
detail.
I
just
wondered:
is
this
like
a
it's,
not
just
like
a
Frontline
front-end
tool,
collecting
data
right?
It's
it
says
on
its
own
database,
to
collect
all
information
and
visualize
from
that
Central
database.
F
Usually,
my
understanding
of
the
city
event
is
just
the
the
the
formats.
Basically,
you
know
tactile
talking
to
Captain
and
it's
just
the
format.
Is
you
same
it's,
but
but
you're.
If
you
visualize
it,
are
you
collecting
all
the
data
into
that
visualizer
database
and
participate
from
there
or
is
it.
D
Yeah
so
right
now
it
is
not
a
database
like
as
in
for
the
different
tools
for
CD
events,
aware
tools,
so
we
are
actually
using
a
cache.
So
it's
not
really
picking
from
DB
as
in
when
the
events
come
so
it
it
builds
upon
a
cache
within
the
CD,
even
somewhere
tool
and
then
use
that,
but
for
promoters
and
grafana
dashboard,
so
we're
actually
using
a
a
DB.
So
that
is
the
graph
database
at
angodb.
D
So
when
the
events
comes
in
so
the
events
with
the
format,
so
it
will
be
stored
in
the
Rango
DB
and
read
by
graphene
dashboard
so
but
yeah.
So
it's
not.
F
Apparently
yeah
I
think
I
I
got
it
now
so
so,
basically,
the
actual
event
is
is
between
the
tools.
The
visualization
tool
is
only
storing
the
it's.
Not
it's,
not
storing
anything
that
the
the
the
cicd
workflow
need
is
just
for
realization.
Only
that's
why
it's
a
cache.
Okay,
all
right!
Thanks!
Yes,
yes,.
B
A
Yeah
I
agree
and
also
the
tool
itself.
I
mean
we
could
probably,
if
you
would
replace
tecton
with,
say,
Argo
workflows,
and
there
was
another
workflow
Event
Center
as
well,
then
the
you
need
to
change
anything
in
the
visualization
layer.
Absolutely
it
can
do
the
same.
So
that's
I
mean
it's.
The
protocol
is
generic
not
and
it
was
diagnostic,
so
it
should
be.
A
That
would
also
that
should
be
a
very
good
showcase
here
that
you
would
be
able
to
like
replace
one
one
tool
of
one
kind
to
another
tool
of
the
same
kind,
still
sending
the
events
or
listening
to
events
and
seeing
that
there
is
no
need
to
change
anything
in
visualization
layer,
but
that's
probably
for
the
next.
The
next
step.
D
So
one
thing
about
the
links
also
I
wanted
to
just
update,
so
we
are
like
this.
Existing
segments
box
still
uses
the
old
specification
of
the
events,
because
that
doesn't
have
links
even
it
doesn't
comply
with
the
latest
specification.
The
event,
so
we
had
a
plan
to
upgrade
the
segment
Spock
as
well
as
the
same,
the
visualization,
also
using
the
latest
specification
so
but
yeah.
D
So
definitely
we
can
do
once
the
links
are
introduced,
so
that
will
be
changed
to
the
latest
specification
with
links
and
as
per
that
like
we
can
also
change
the
logic
that
we
have
assumed
links
between
the
events,
so
it
can
be
replaced
with
what
exactly
comes
from
the
CD
events
once
that
is
finalized.
A
C
E
Yes,
so
I
help
with
organ
or
CDF
me
online
meetups
per
year
for
the
CD
Foundation.
E
They're
all
just
online
meetups,
it
creates
nice
content,
though,
and
we
can
and
we'd
be
able
to
capture
a
pretty
nice
recording
of
the
demo
doing
that.
E
You
know
we
don't
have
to
be
honest,
we
don't
get
a
huge
audience
on
those
CD
events
meetups
the
day
of
the
Meetup,
but
they
do
really
well
post
post.
You
know
posting.
E
Yeah
I
think
most
people
they
they
look
pretty
on
demand,
instead
of
actually
being
there
yeah
and
it's
something
like
CD
events.
We
are
we,
you
know
we
continue
to
try
to
shake
the
trees
and
get
people
to
be
more
interested
in
it.
I
can
say
in
the
past
until
it's
got
something
visual
Associated
to
it.
It's
oftentimes
hard
for
people
to
conceptualize
it.
E
So
we
have
had
some
difficulty
getting
more
people
to
kind
of
bite
down
and
understand
what
we're
trying
to
do,
but
as
soon
as
we
have
something
more
visual
I
think
that
it
will
be
easier
for
us
to
evangelize
around
it.
C
Very
good,
very
good,
and
maybe
jalander
we
can
look
at
at
put
as
Tracy
said,
putting
it
in
the
Box,
because
what
we've
found
Tracy
is
the
the
grafana
utility
you
can
it's
very
easy
to
visualize,
whatever
you
need
to
see.
So
if
we
put
made
that
available
to
people,
they
could
write
their
own
queries.
E
C
A
E
A
Think
it's
marked
for
Oktoberfest
I,
intended
to
write
an
issue
for
it.
The
way
we
did
last
year
would
you
still
want
to
do
the
blog
post,
for
it
I
mean
unless
you
we
didn't
even
have
a
blog
post,
but
but.
E
E
Us
where
our
repos
are
and
I
will
not
I
hope,
and
then
you
guys
are
going
to
mark
them
Oktoberfest
before
October
1st,
so
we
have
a
month
to
get
those
those
marked.
A
B
E
Point
them
to
the
repo,
then
that
should
be
fine
I'm
assuming
right
now
we
will,
we
won't
be
referring
to
I.
Think.
Let
me
look
at
the
Milestones,
so
I,
don't
sound
like
I
completely,
don't
understand
what
we're
doing
I
know
we
have
a
couple
of
Milestones
out
there.
In
fact,
one
of
them
we
were
supposed
to
have
done
this
month
and
we
need
a
Blog
for
that,
but
I've
I've
just
told
Roxanne,
to
give
it
some
time.
E
A
But
I,
don't
we
haven't?
We
don't
have
a
milestone
for
the
Oktoberfest
part.
E
C
A
There
so
either
that
or
if
I
create
an
issue,
the
proper
way
that
we
did
last
time
it
might
be
better
to
have
it
that
way,
because
then.
E
We
can
yeah,
so
if
you
want,
if
you
want
to
create,
do
that,
if
you
could
send
it
get
it
done
and
send
it
to
me
today,
because
I.
A
C
E
And
then
we
are,
we
were
going
to
have
a
release
announcement,
this
I
think
now,
but
I'm,
assuming
we
probably
should
give
it
two
weeks.
E
A
E
A
Yeah
yeah
so
we'll
see
when
we
are
all
there
I'll
see.
Now
we
have
the
zero
three
Milestone
is
already
done,
which
is
still
in
it
doesn't
State
it's
done,
but
it's
done.
It
should
be
closed.
So
it's
serious
whole
Milestone
that
we
are
aiming
for
now,
but
it's
not
due
by
August
31st,
as
it
said,
they're
in
the
Milestone.
So.
E
Just
give
me
that
just
just
shoot
me
an
email
with
that
issue
that
you
want
to
direct
people
to
for.
E
And
I'll
worry
about
trying
to
get
a
Blog
for
a
new
release
done
by
the
end
of
September
I'm,
going
to
be
out
for
two
weeks,
though
so,
but.
F
D
D
I'm
not
able
to
stop
yeah
no.
A
No,
it's
not
sharing
me!
Okay!
Thank
you!
So
I
guess
that's
it
for
today,
though,
talk
to
you
next
time,
thanks
for
your
attendance
today,
thank.