Needs you
Needs you 15
Infrastructure 12
-
UrgentInternal DNS records have never been read
- Rule
- Something has not been read for days
kind-never-swept - Severity
- serious
- Defined at
hq/platform/application/controller_findings.py:146- Stands in for
skipped-by-a-sweepnever-observed- From
- Infrastructure
- Key
hq.infrastructure:finding:kind-never-swept:adguard.rewrite
What HQ shows for them is only what was entered in HQ. Read them now. If that fails, the connection that reads them needs fixing.
- Last read
- never
- In HQ
- 2
- Read every
- 5 minutes
-
UrgentThe controller on example-controller has not read 2 types of record
- Rule
- The controller has stopped reading
controller-sweep-stale - Severity
- serious
- Defined at
hq/platform/application/controller_findings.py:211- Stands in for
kind-never-swept- From
- Infrastructure
- Key
hq.infrastructure:finding:controller-sweep-stale:controller:e61d92aae82ff989
Everything listed is read by the same controller, so check it first.
- Not read
- Domains, Proxy hosts
-
Check the controller is running
ssh example-controller "sudo systemctl status severino-hq-controller.service --no-pager" -
Read its log
ssh example-controller "sudo journalctl -u severino-hq-controller.service -n 50 --no-pager"
Urgent A container no compose project started 8
-
UrgentUnrecognised container example-service-with-a-long-name-0 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-0
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-0"
-
UrgentUnrecognised container example-service-with-a-long-name-1 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-1
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-1"
-
UrgentUnrecognised container example-service-with-a-long-name-2 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-2
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-2"
-
UrgentUnrecognised container example-service-with-a-long-name-3 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-3
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-3"
-
UrgentUnrecognised container example-service-with-a-long-name-4 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-4
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-4"
-
UrgentUnrecognised container example-service-with-a-long-name-5 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-5
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-5"
-
UrgentUnrecognised container example-service-with-a-long-name-6 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-6
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-6"
-
UrgentUnrecognised container example-service-with-a-long-name-7 on app-host
- Rule
- A container no compose project started
unrecognised-container - Severity
- serious
- Defined at
hq/platform/application/docker_estate.py:283- From
- Infrastructure
- Key
hq.infrastructure:finding:unrecognised-container:machine:app-host
No compose project started it, so HQ is not tracking it. Adopt it if you started it. Otherwise find what did and remove it.
- Container
- example-service-with-a-long-name-7
- Machine
- app-host
-
If nothing needs it, remove it from app-host
ssh app-host "sudo docker rm -f example-service-with-a-long-name-7"
-
Urgenthq.example.com leads to example-service-with-a-long-name-0 on app-host, which is stopped
- Rule
- A route to a container that is not running
route-to-stopped-container - Severity
- serious
- Defined at
hq/platform/application/contradiction_findings.py:467- From
- Infrastructure
- Key
hq.infrastructure:finding:route-to-stopped-container:service:hq.example.com
Requests for hq.example.com fail until example-service-with-a-long-name-0 runs again or the proxy route points at what replaced it.
- Name
- hq.example.com
- Path
- Internal DNS → Tailnet → app-host → Proxy host → example-service-with-a-long-name-0
- Container
- stopped
-
Start example-service-with-a-long-name-0 on app-host
ssh app-host "sudo docker start example-service-with-a-long-name-0"
-
Needs attentionexample-npm: the address is not Nginx Proxy Manager's API
- Rule
- A connection is not answering
connection-not-answering - Severity
- attention
- Defined at
hq/platform/application/connection_findings.py:19- From
- Infrastructure
- Key
hq.infrastructure:finding:connection-not-answering:connection:infrastructure.controllers:example-controller:example-npm
The address answered with a sign-in page at sso.example.com, not the API. Use the provider's direct API address. HQ cannot read anything through it, so what it shows from example-npm may be out of date.
- State
- Not answering
- Cause
- The address is not the API
- Last checked
- just now
-
Point the connection at Nginx Proxy Manager's own API address
HQ cannot change 1Password or your network.
Expenses 1
Services 2
-
Needs attentionapp.example.com is not set up properly
- From
- Services
- Key
hq.services:service:app.example.com
Resolves to 192.0.2.10, a documentation address. Nothing answers there.
-
Needs attentionhq.example.com is not set up properly
- From
- Services
- Key
hq.services:service:hq.example.com
Resolves to 192.0.2.10, a documentation address. Nothing answers there.