-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(metricsforwarder): Directly write to Log Cache via Syslog protocol #2913
Conversation
ca_file: metron_client/ca.crt | ||
db: | ||
policy_db: | ||
url: postgres://postgres:CHANGE_ME@some-service:5432/autoscaler |
Check failure
Code scanning / SonarCloud
PostgreSQL database passwords should not be disclosed
connection_max_lifetime: 60s | ||
|
||
storedprocedure_db: | ||
url: postgres://postgres:CHANGE_ME@some-service:5432/autoscaler |
Check failure
Code scanning / SonarCloud
PostgreSQL database passwords should not be disclosed
b2abedd
to
6718757
Compare
5da618c
to
f6ef81b
Compare
6ec0348
to
b6a52a1
Compare
a3d39de
to
676613d
Compare
Long deployments names generate longer than posible urls and can break certificate generation process when running a bosh deploy.
…log" This reverts commit 5ad72de.
Prometheus metrics and health enpoint will be address globally once the we know whats the best way to address this issue when running autoscaler components as cf apps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice and clean PR!
thanks also for making the world a better place by improving the pipeline creation, fixing the test-certs folders etc. 👍
Quality Gate passedIssues Measures |
Rebase failed
As part of an ongoing effort to get app autoscaler components running on CF, an alternative way to send custom metrics to log-cache from metricforwarder needs to be found.
Current implementation relays on direct connection within the metrics forwarder VM to a locally run metro-agent process. If the goals is to get Metricfowarder running as a CF app, CF container would need access to a metron-agent on the host machine, in this case a Diego cell, which would not be set up by as the same way it is being run now.
Alternatively we can relay on the log-cache syslog-server, while opening traffic from a cf container to the log-cache vm provision by the CF deployment.
This PR intends to default metricforwarder to write to the syslog-server directly instead of using a locally running agent.