[jira] [Closed] (FLINK-11561) Translate "Flink Architecture" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong closed FLINK-11561. - Resolution: Fixed > Translate "Flink Architecture" page into Chinese > > > Key: FLINK-11561 > URL: https://issues.apache.org/jira/browse/FLINK-11561 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Assignee: Tom Goong >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Translate "Flink Architecture" page into Chinese. > The markdown file is located in: flink-web/flink-architecture.zh.md > The url link is: https://flink.apache.org/zh/flink-architecture.html > Please adjust the links in the page to Chinese pages when translating. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLINK-11561) Translate "Flink Architecture" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840919#comment-16840919 ] Tom Goong commented on FLINK-11561: --- [~jark] sorry, Can not be separated recently, it'll be done before weekend。 > Translate "Flink Architecture" page into Chinese > > > Key: FLINK-11561 > URL: https://issues.apache.org/jira/browse/FLINK-11561 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Assignee: Tom Goong >Priority: Major > > Translate "Flink Architecture" page into Chinese. > The markdown file is located in: flink-web/flink-architecture.zh.md > The url link is: https://flink.apache.org/zh/flink-architecture.html > Please adjust the links in the page to Chinese pages when translating. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-11634) Translate "State Backends" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong reassigned FLINK-11634: - Assignee: (was: Tom Goong) > Translate "State Backends" page into Chinese > > > Key: FLINK-11634 > URL: https://issues.apache.org/jira/browse/FLINK-11634 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Documentation >Reporter: Congxian Qiu(klion26) >Priority: Major > > doc locates in flink/docs/dev/stream/state/state_backens.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-11637) Translate "Checkpoints" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong reassigned FLINK-11637: - Assignee: (was: Tom Goong) > Translate "Checkpoints" page into Chinese > - > > Key: FLINK-11637 > URL: https://issues.apache.org/jira/browse/FLINK-11637 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Documentation >Reporter: Congxian Qiu(klion26) >Priority: Major > > doc locates in flink/docs/ops/state/checkpoints.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLINK-11561) Translate "Flink Architecture" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834343#comment-16834343 ] Tom Goong commented on FLINK-11561: --- [~jark] Sorry, I thought that the flink-parent documentation should be put together with flink-web. Actually I am wrong > Translate "Flink Architecture" page into Chinese > > > Key: FLINK-11561 > URL: https://issues.apache.org/jira/browse/FLINK-11561 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Assignee: Tom Goong >Priority: Major > > Translate "Flink Architecture" page into Chinese. > The markdown file is located in: flink-web/flink-architecture.zh.md > The url link is: https://flink.apache.org/zh/flink-architecture.html > Please adjust the links in the page to Chinese pages when translating. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLINK-11561) Translate "Flink Architecture" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834331#comment-16834331 ] Tom Goong commented on FLINK-11561: --- this file is located in "flink-web" project. Will they be merged together in the future? > Translate "Flink Architecture" page into Chinese > > > Key: FLINK-11561 > URL: https://issues.apache.org/jira/browse/FLINK-11561 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Assignee: Tom Goong >Priority: Major > > Translate "Flink Architecture" page into Chinese. > The markdown file is located in: flink-web/flink-architecture.zh.md > The url link is: https://flink.apache.org/zh/flink-architecture.html > Please adjust the links in the page to Chinese pages when translating. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-11637) Translate "Checkpoints" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong reassigned FLINK-11637: - Assignee: Tom Goong > Translate "Checkpoints" page into Chinese > - > > Key: FLINK-11637 > URL: https://issues.apache.org/jira/browse/FLINK-11637 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Documentation >Reporter: Congxian Qiu(klion26) >Assignee: Tom Goong >Priority: Major > > doc locates in flink/docs/ops/state/checkpoints.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-11634) Translate "State Backends" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong reassigned FLINK-11634: - Assignee: Tom Goong > Translate "State Backends" page into Chinese > > > Key: FLINK-11634 > URL: https://issues.apache.org/jira/browse/FLINK-11634 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Documentation >Reporter: Congxian Qiu(klion26) >Assignee: Tom Goong >Priority: Major > > doc locates in flink/docs/dev/stream/state/state_backens.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-11561) Translate "Flink Architecture" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong reassigned FLINK-11561: - Assignee: Tom Goong > Translate "Flink Architecture" page into Chinese > > > Key: FLINK-11561 > URL: https://issues.apache.org/jira/browse/FLINK-11561 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Assignee: Tom Goong >Priority: Major > > Translate "Flink Architecture" page into Chinese. > The markdown file is located in: flink-web/flink-architecture.zh.md > The url link is: https://flink.apache.org/zh/flink-architecture.html > Please adjust the links in the page to Chinese pages when translating. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-12014) Flink CEP Doc missing "SkipToNextStrategy"
[ https://issues.apache.org/jira/browse/FLINK-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong updated FLINK-12014: -- Description: in cep.md file，The following description misses *SkipToNextStrategy：* *After Match Skip Strategy* For a given pattern, the same event may be assigned to multiple successful matches. To control to how many matches an event will be assigned, you need to specify the skip strategy called `AfterMatchSkipStrategy`. There are four types of skip strategies, listed as follows: * *NO_SKIP*: Every possible match will be emitted. * *SKIP_PAST_LAST_EVENT*: Discards every partial match that started after the match started but before it ended. * *SKIP_TO_FIRST*: Discards every partial match that started after the match started but before the first event of *PatternName* occurred. * *SKIP_TO_LAST*: Discards every partial match that started after the match started but before the last event of *PatternName* occurred. was: in cep.md file，The following description misses *SkipToNextStrategy* ### After Match Skip Strategy For a given pattern, the same event may be assigned to multiple successful matches. To control to how many matches an event will be assigned, you need to specify the skip strategy called `AfterMatchSkipStrategy`. There are four types of skip strategies, listed as follows: * *NO_SKIP*: Every possible match will be emitted. * *SKIP_PAST_LAST_EVENT*: Discards every partial match that started after the match started but before it ended. * *SKIP_TO_FIRST*: Discards every partial match that started after the match started but before the first event of *PatternName* occurred. * *SKIP_TO_LAST*: Discards every partial match that started after the match started but before the last event of *PatternName* occurred. > Flink CEP Doc missing "SkipToNextStrategy" > -- > > Key: FLINK-12014 > URL: https://issues.apache.org/jira/browse/FLINK-12014 > Project: Flink > Issue Type: Bug > Components: Documentation >Reporter: Tom Goong >Assignee: Tom Goong >Priority: Major > > in cep.md file，The following description misses *SkipToNextStrategy：* > > *After Match Skip Strategy* > For a given pattern, the same event may be assigned to multiple successful > matches. To control to how many matches an event will be assigned, you need > to specify the skip strategy called `AfterMatchSkipStrategy`. There are four > types of skip strategies, listed as follows: > * *NO_SKIP*: Every possible match will be emitted. > * *SKIP_PAST_LAST_EVENT*: Discards every partial match that > started after the match started but before it ended. > * *SKIP_TO_FIRST*: Discards every partial match that > started after the match started but before the first event of *PatternName* > occurred. > * *SKIP_TO_LAST*: Discards every partial match that started > after the match started but before the last event of *PatternName* occurred. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12014) Flink CEP Doc missing "SkipToNextStrategy"
Tom Goong created FLINK-12014: - Summary: Flink CEP Doc missing "SkipToNextStrategy" Key: FLINK-12014 URL: https://issues.apache.org/jira/browse/FLINK-12014 Project: Flink Issue Type: Bug Components: Documentation Reporter: Tom Goong Assignee: Tom Goong in cep.md file，The following description misses *SkipToNextStrategy* ### After Match Skip Strategy For a given pattern, the same event may be assigned to multiple successful matches. To control to how many matches an event will be assigned, you need to specify the skip strategy called `AfterMatchSkipStrategy`. There are four types of skip strategies, listed as follows: * *NO_SKIP*: Every possible match will be emitted. * *SKIP_PAST_LAST_EVENT*: Discards every partial match that started after the match started but before it ended. * *SKIP_TO_FIRST*: Discards every partial match that started after the match started but before the first event of *PatternName* occurred. * *SKIP_TO_LAST*: Discards every partial match that started after the match started but before the last event of *PatternName* occurred. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-11867) mistaking in checking filePath's value
[
https://issues.apache.org/jira/browse/FLINK-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Goong updated FLINK-11867:
--
Component/s: (was: Build System)
> mistaking in checking filePath's value
> --
>
> Key: FLINK-11867
> URL: https://issues.apache.org/jira/browse/FLINK-11867
> Project: Flink
> Issue Type: Bug
>Reporter: Tom Goong
>Assignee: Tom Goong
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In class StreamExecutionEnvironment
>
> {code:java}
> // code placeholder
> public DataStreamSource readTextFile(String filePath, String
> charsetName) {
> Preconditions.checkNotNull(filePath, "The file path must not be null.");
> Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
> empty.");
> TextInputFormat format = new TextInputFormat(new Path(filePath));
> format.setFilesFilter(FilePathFilter.createDefaultFilter());
> TypeInformation typeInfo = BasicTypeInfo.STRING_TYPE_INFO;
> format.setCharsetName(charsetName);
> return readFile(format, filePath, FileProcessingMode.PROCESS_ONCE, -1,
> typeInfo);
> }
> {code}
>
> the *Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not
> be empty.");* this will not work
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-11867) mistaking in checking filePath's value
[
https://issues.apache.org/jira/browse/FLINK-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Goong updated FLINK-11867:
--
Description:
In class StreamExecutionEnvironment
{code:java}
// code placeholder
public DataStreamSource readTextFile(String filePath, String
charsetName) {
Preconditions.checkNotNull(filePath, "The file path must not be null.");
Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
empty.");
TextInputFormat format = new TextInputFormat(new Path(filePath));
format.setFilesFilter(FilePathFilter.createDefaultFilter());
TypeInformation typeInfo = BasicTypeInfo.STRING_TYPE_INFO;
format.setCharsetName(charsetName);
return readFile(format, filePath, FileProcessingMode.PROCESS_ONCE, -1,
typeInfo);
}
{code}
the *Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
empty.");* this will not work
was:
In class StreamExecutionEnvironment
{code:java}
// code placeholder
public DataStreamSource readTextFile(String filePath, String
charsetName) {
Preconditions.checkNotNull(filePath, "The file path must not be null.");
Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
empty.");
TextInputFormat format = new TextInputFormat(new Path(filePath));
format.setFilesFilter(FilePathFilter.createDefaultFilter());
TypeInformation typeInfo = BasicTypeInfo.STRING_TYPE_INFO;
format.setCharsetName(charsetName);
return readFile(format, filePath, FileProcessingMode.PROCESS_ONCE, -1,
typeInfo);
}
{code}
the `Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
empty.");` this will not work
> mistaking in checking filePath's value
> --
>
> Key: FLINK-11867
> URL: https://issues.apache.org/jira/browse/FLINK-11867
> Project: Flink
> Issue Type: Bug
> Components: Build System
>Reporter: Tom Goong
>Assignee: Tom Goong
>Priority: Major
>
> In class StreamExecutionEnvironment
>
> {code:java}
> // code placeholder
> public DataStreamSource readTextFile(String filePath, String
> charsetName) {
> Preconditions.checkNotNull(filePath, "The file path must not be null.");
> Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
> empty.");
> TextInputFormat format = new TextInputFormat(new Path(filePath));
> format.setFilesFilter(FilePathFilter.createDefaultFilter());
> TypeInformation typeInfo = BasicTypeInfo.STRING_TYPE_INFO;
> format.setCharsetName(charsetName);
> return readFile(format, filePath, FileProcessingMode.PROCESS_ONCE, -1,
> typeInfo);
> }
> {code}
>
> the *Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not
> be empty.");* this will not work
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-11867) mistaking in checking filePath's value
[
https://issues.apache.org/jira/browse/FLINK-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Goong updated FLINK-11867:
--
Description:
In class StreamExecutionEnvironment
{code:java}
// code placeholder
public DataStreamSource readTextFile(String filePath, String
charsetName) {
Preconditions.checkNotNull(filePath, "The file path must not be null.");
Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
empty.");
TextInputFormat format = new TextInputFormat(new Path(filePath));
format.setFilesFilter(FilePathFilter.createDefaultFilter());
TypeInformation typeInfo = BasicTypeInfo.STRING_TYPE_INFO;
format.setCharsetName(charsetName);
return readFile(format, filePath, FileProcessingMode.PROCESS_ONCE, -1,
typeInfo);
}
{code}
the `Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
empty.");` this will not work
> mistaking in checking filePath's value
> --
>
> Key: FLINK-11867
> URL: https://issues.apache.org/jira/browse/FLINK-11867
> Project: Flink
> Issue Type: Bug
> Components: Build System
>Reporter: Tom Goong
>Assignee: Tom Goong
>Priority: Major
>
> In class StreamExecutionEnvironment
>
> {code:java}
> // code placeholder
> public DataStreamSource readTextFile(String filePath, String
> charsetName) {
> Preconditions.checkNotNull(filePath, "The file path must not be null.");
> Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be
> empty.");
> TextInputFormat format = new TextInputFormat(new Path(filePath));
> format.setFilesFilter(FilePathFilter.createDefaultFilter());
> TypeInformation typeInfo = BasicTypeInfo.STRING_TYPE_INFO;
> format.setCharsetName(charsetName);
> return readFile(format, filePath, FileProcessingMode.PROCESS_ONCE, -1,
> typeInfo);
> }
> {code}
>
> the `Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not
> be empty.");` this will not work
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FLINK-11867) mistaking in checking filePath's value
Tom Goong created FLINK-11867: - Summary: mistaking in checking filePath's value Key: FLINK-11867 URL: https://issues.apache.org/jira/browse/FLINK-11867 Project: Flink Issue Type: Bug Components: Build System Reporter: Tom Goong Assignee: Tom Goong -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-11742) Push metrics to Pushgateway without "instance"
[
https://issues.apache.org/jira/browse/FLINK-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Goong updated FLINK-11742:
--
Description:
According to the official article,
[https://prometheus.io/docs/concepts/jobs_instances/]
[https://github.com/prometheus/pushgateway]
when sending a metric to Prometheus Pushgateway, you need to give an "instance"
message.
In actual use, after there is no "instance", Prometheus stores metrics with
problems, metrics are not continuous, and a lot of data is lost. After adding
instance, it returns to normal.
no "instance"
!image-2019-02-25-17-16-28-618.png!
with "instance"
!image-2019-02-25-17-16-59-034.png!
{quote}In Prometheus terms, an endpoint you can scrape is called an instance,
usually corresponding to a single process. A collection of instances with the
same purpose, a process replicated for scalability or reliability for example,
is called a job.
{quote}
{quote}For example, an API server job with four replicated instances:
job: api-server
-- instance 1: 1.2.3.4:5670
-- instance 2: 1.2.3.4:5671
-- instance 3: 5.6.7.8:5670
-- instance 4: 5.6.7.8:5671
{quote}
[https://prometheus.io/docs/concepts/jobs_instances/#jobs-and-instances]
I think a Flink job corresponds to a Prometheus job, and taskmanager and
jobmanager correspond to different instances. If the jobName is used as the
instance label, the same metrics of different tasksmanages will conflict, and
operations such as sum will fail.
was:
According to the official article,
[https://prometheus.io/docs/concepts/jobs_instances/]
[https://github.com/prometheus/pushgateway]
when sending a metric to Prometheus Pushgateway, you need to give an "instance"
message.
In actual use, after there is no "instance", Prometheus stores metrics with
problems, metrics are not continuous, and a lot of data is lost. After adding
instance, it returns to normal.
no "instance"
!image-2019-02-25-17-16-28-618.png!
with "instance"
!image-2019-02-25-17-16-59-034.png!
> Push metrics to Pushgateway without "instance"
> --
>
> Key: FLINK-11742
> URL: https://issues.apache.org/jira/browse/FLINK-11742
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics
>Reporter: Tom Goong
>Assignee: Tom Goong
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2019-02-25-17-16-28-618.png,
> image-2019-02-25-17-16-59-034.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> According to the official article,
> [https://prometheus.io/docs/concepts/jobs_instances/]
> [https://github.com/prometheus/pushgateway]
> when sending a metric to Prometheus Pushgateway, you need to give an
> "instance" message.
> In actual use, after there is no "instance", Prometheus stores metrics with
> problems, metrics are not continuous, and a lot of data is lost. After adding
> instance, it returns to normal.
>
> no "instance"
> !image-2019-02-25-17-16-28-618.png!
>
> with "instance"
> !image-2019-02-25-17-16-59-034.png!
>
>
> {quote}In Prometheus terms, an endpoint you can scrape is called an instance,
> usually corresponding to a single process. A collection of instances with the
> same purpose, a process replicated for scalability or reliability for
> example, is called a job.
> {quote}
> {quote}For example, an API server job with four replicated instances:
> job: api-server
> -- instance 1: 1.2.3.4:5670
> -- instance 2: 1.2.3.4:5671
> -- instance 3: 5.6.7.8:5670
> -- instance 4: 5.6.7.8:5671
> {quote}
> [https://prometheus.io/docs/concepts/jobs_instances/#jobs-and-instances]
> I think a Flink job corresponds to a Prometheus job, and taskmanager and
> jobmanager correspond to different instances. If the jobName is used as the
> instance label, the same metrics of different tasksmanages will conflict, and
> operations such as sum will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FLINK-11742) Push metrics to Pushgateway without "instance"
[ https://issues.apache.org/jira/browse/FLINK-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782592#comment-16782592 ] Tom Goong commented on FLINK-11742: --- I need to monitor some conditions of different taskmanagers. But if there is no given instance or the correct distinction between different taximanagers, putgateway will be treated as one, resulting in data loss and line discontinuity. > Push metrics to Pushgateway without "instance" > -- > > Key: FLINK-11742 > URL: https://issues.apache.org/jira/browse/FLINK-11742 > Project: Flink > Issue Type: Bug > Components: Runtime / Metrics >Reporter: Tom Goong >Assignee: Tom Goong >Priority: Major > Labels: pull-request-available > Attachments: image-2019-02-25-17-16-28-618.png, > image-2019-02-25-17-16-59-034.png > > Time Spent: 10m > Remaining Estimate: 0h > > According to the official article, > [https://prometheus.io/docs/concepts/jobs_instances/] > [https://github.com/prometheus/pushgateway] > when sending a metric to Prometheus Pushgateway, you need to give an > "instance" message. > In actual use, after there is no "instance", Prometheus stores metrics with > problems, metrics are not continuous, and a lot of data is lost. After adding > instance, it returns to normal. > > no "instance" > !image-2019-02-25-17-16-28-618.png! > > with "instance" > !image-2019-02-25-17-16-59-034.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-11742) Push metrics to Pushgateway without "instance"
[ https://issues.apache.org/jira/browse/FLINK-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong updated FLINK-11742: -- Summary: Push metrics to Pushgateway without "instance" (was: Push metrics t0 Pushgateway without "instance") > Push metrics to Pushgateway without "instance" > -- > > Key: FLINK-11742 > URL: https://issues.apache.org/jira/browse/FLINK-11742 > Project: Flink > Issue Type: Bug > Components: Metrics >Reporter: Tom Goong >Assignee: Tom Goong >Priority: Major > Attachments: image-2019-02-25-17-16-28-618.png, > image-2019-02-25-17-16-59-034.png > > > According to the official article, > [https://prometheus.io/docs/concepts/jobs_instances/] > [https://github.com/prometheus/pushgateway] > when sending a metric to Prometheus Pushgateway, you need to give an > "instance" message. > In actual use, after there is no "instance", Prometheus stores metrics with > problems, metrics are not continuous, and a lot of data is lost. After adding > instance, it returns to normal. > > no "instance" > !image-2019-02-25-17-16-28-618.png! > > with "instance" > !image-2019-02-25-17-16-59-034.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-11742) Push metrics t0 Pushgateway without "instance"
[ https://issues.apache.org/jira/browse/FLINK-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong updated FLINK-11742: -- Description: According to the official article, [https://prometheus.io/docs/concepts/jobs_instances/] [https://github.com/prometheus/pushgateway] when sending a metric to Prometheus Pushgateway, you need to give an "instance" message. In actual use, after there is no "instance", Prometheus stores metrics with problems, metrics are not continuous, and a lot of data is lost. After adding instance, it returns to normal. no "instance" !image-2019-02-25-17-16-28-618.png! with "instance" !image-2019-02-25-17-16-59-034.png! was: According to the official article, [https://prometheus.io/docs/concepts/jobs_instances/] [https://github.com/prometheus/pushgateway] when sending a metric to Prometheus Pushgateway, you need to give an "instance" message. In actual use, after there is no "instance", Prometheus stores metrics with problems, metrics are not continuous, and a lot of data is lost. After adding instance, it returns to normal. !image-2019-02-25-17-16-28-618.png! !image-2019-02-25-17-16-59-034.png! > Push metrics t0 Pushgateway without "instance" > -- > > Key: FLINK-11742 > URL: https://issues.apache.org/jira/browse/FLINK-11742 > Project: Flink > Issue Type: Bug > Components: Metrics >Reporter: Tom Goong >Assignee: Tom Goong >Priority: Major > Attachments: image-2019-02-25-17-16-28-618.png, > image-2019-02-25-17-16-59-034.png > > > According to the official article, > [https://prometheus.io/docs/concepts/jobs_instances/] > [https://github.com/prometheus/pushgateway] > when sending a metric to Prometheus Pushgateway, you need to give an > "instance" message. > In actual use, after there is no "instance", Prometheus stores metrics with > problems, metrics are not continuous, and a lot of data is lost. After adding > instance, it returns to normal. > > no "instance" > !image-2019-02-25-17-16-28-618.png! > > with "instance" > !image-2019-02-25-17-16-59-034.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-11742) Push metrics t0 Pushgateway without "instance"
Tom Goong created FLINK-11742: - Summary: Push metrics t0 Pushgateway without "instance" Key: FLINK-11742 URL: https://issues.apache.org/jira/browse/FLINK-11742 Project: Flink Issue Type: Bug Components: Metrics Reporter: Tom Goong Assignee: Tom Goong Attachments: image-2019-02-25-17-16-28-618.png, image-2019-02-25-17-16-59-034.png According to the official article, [https://prometheus.io/docs/concepts/jobs_instances/] [https://github.com/prometheus/pushgateway] when sending a metric to Prometheus Pushgateway, you need to give an "instance" message. In actual use, after there is no "instance", Prometheus stores metrics with problems, metrics are not continuous, and a lot of data is lost. After adding instance, it returns to normal. !image-2019-02-25-17-16-28-618.png! !image-2019-02-25-17-16-59-034.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLINK-11613) Translate the "Project Template for Scala" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Goong reassigned FLINK-11613: - Assignee: Tom Goong > Translate the "Project Template for Scala" page into Chinese > > > Key: FLINK-11613 > URL: https://issues.apache.org/jira/browse/FLINK-11613 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Documentation >Reporter: Jark Wu >Assignee: Tom Goong >Priority: Major > > The page url is > https://ci.apache.org/projects/flink/flink-docs-master/dev/projectsetup/scala_api_quickstart.html > The markdown file is located in > flink/docs/dev/projectsetup/scala_api_quickstart.zh.md > The markdown file will be created once FLINK-11529 is merged. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
