Hi Chesnay, Elaborating the use case, for example I have 3 operators :
Operator A(parallelism 1, running on taskmanager1) --> Operator B(parallelism 3, running on taskmanager1, taskmanager2) --> Operator C(Parallelism 1, running on taskmanager1). Suppose there are 10 records in process since Operator A,C running on same task manager so we get the same metric count for operator A and C. Since Operator B instances are running on taskmanager1 & taskmanager2 at time it shows less number of records as compare to operator A & C. Since scrapping is based on target end points and taskmanager1 / taskmanager2 are running on different targets with different last scrape interval. Regards, Bhawana On Thu, Aug 26, 2021 at 4:29 PM Chesnay Schepler <ches...@apache.org> wrote: > I'm not sure I understand what the desired behavior would be. > > Is it that you want metrics on each TM to be scraped in a well-defined > order? I.e., first all metrics of Operator A, then all metrics of Operator > B and so on? > > Maybe you could provide an example to make things clear. > > On 26/08/2021 08:15, bhawana gupta wrote: > > Hello, > > Please suggest. > > Regards, > Bhawana > > On Wed, Aug 25, 2021 at 5:07 PM bhawana gupta <bhawanabhumc...@gmail.com> > wrote: > >> Hi, >> >> We are using prometheus reporter to fetch metrics (flink 1.12.1 on k8s >> environment). We were facing an issue since the prometheus reporter has >> various targets corresponding to each job & task manager hence the >> different scraping for each target causing syncing issue in metrics count >> for various operators with-in a given time scrape. >> Is it possible to configure prometheus reporter so that all operators are >> scraped in a sequenced way for a given scrape interval irrespective of >> target? >> >> Regards, >> Bhawana >> > >
